-
Notifications
You must be signed in to change notification settings - Fork 97
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
fix(tabs)!: tabscontroller refactor #2699
Conversation
let tabscontroller handle the aria stuff only, for the most part. Total separation between RTIC and tabs state. Disabled tabs are still able to be focused via RTIC, just that they can't change the Tab's active tab state. Use context instead of cascade Use shadow classes instead of reflected attrs (but keep the attrs for now to avoid breaking changes)
🦋 Changeset detectedLatest commit: 0d19f99 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for patternfly-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Should we now say that if Right now the component becomes selectable. |
The idea is that users should not set aria attrs on any tab elements. They should only and always use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given resolution of last remaining open comment
Lifted Granite Tall Mountains
Closes #2695
What I did
Total separation between RTIC and tabs state. Disabled tabs are still able to be focused via RTIC, just that they can't change the Tab's active tab state.
Remove most of tabscontroller's logic in favour of context, rtic.
Testing Instructions