Skip to content

Conversation

happycollision
Copy link

This builds off of @Msliberty's PR #61

This one, however, doesn't assume that "that the Tab node will always be the grandchild of the Tabs component node". Just that it will be a descendant. Feedback is welcome.

This builds off of @Msliberty's commit at themattliberty@c4b4eaf

This one, however, doesn't assume that "that the Tab node will always be the grandchild of the Tabs component node".
@degr
Copy link

degr commented Apr 18, 2016

+1

@danez danez added the bug label Jun 6, 2016
@danez danez closed this in #103 Jun 11, 2016
danez added a commit that referenced this pull request Jun 11, 2016
Add a check that checks if the tab belongs to the container.

Fixes #54
Fixes #91
@danez
Copy link
Collaborator

danez commented Jun 11, 2016

Thanks for your PR this is now fixed as of 9b5eeae

@kirankashalkar
Copy link

Is this now fixed in the current version?

@joepvl
Copy link
Collaborator

joepvl commented Jul 9, 2016

@kirankashalkar yep, it is! 😄

@happycollision happycollision deleted the another-fix-for-nested-tabs branch July 24, 2016 00:06
@kirankashalkar
Copy link

What version is this exactly fixed in?
0.5.5?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants