-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Features: React 0.14; Specifying visible index for tab panel #6
Comments
Yo! We will be moving the tab system to regular anchors for accessibility reasons (see #11), so you’ll be able to move from one tab to the other just by having a link anchoring to a specific tab. Regarding the initial index, we’re on it. :) |
Regarding React 0.14 compatibility, as far as I can tell the only difference is with |
Most packages seem to offer two versions, an older version that works with 0.13 and a newer one with 0.14. Most of the updates that they then do are on the newer version which supports 0.14.
If you are doing anchor tags, does that also mean changing tabs will change the url in the address bar/history?
Great, thank you! |
Done. |
Okay, the only thing I can think of is cases where a developer might be using the tabs within another component or some part of the page. In that case, they might not want to have the url change change in the address bar/history. Thoughts? |
I disagree. I think hash-based navigation is a key part of a tabbing system. |
Hi @eschaefer! I was trying to make a decision on what react-tab component to use - I really like the simplicity of what you have but there are a couple of features that would be really helpful. I was wondering if you have any plans to add the following features -
visibleIndex
as a prop. Thoughts?visibleIndex
as a prop, I believe.PS. Thank you for your quick response on #5!
Thank you!
The text was updated successfully, but these errors were encountered: