Closed bennypowers closed 4 months ago
Latest commit: 0d19f9963a85de9d2b9e847aeeccebf42bbd0f5e
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
Name | Link |
---|---|
Latest commit | d9bcbb8bac09df0befd51d268c3be56b38671047 |
Deploy Preview | https://deploy-preview-2699--patternfly-elements.netlify.app/ |
To edit notification comments on pull requests, go to your Netlify site settings.
Should we now say that if <pf-tab aria-disabled="true">
is set that this has the same function as <pf-tab disabled>
and update the component accordingly? /cc @nikkimk
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 disabled
when they need that feature
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