Tabs: update styling to more closely match previous implementation #57275
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces #57121
What?
Updates the styling on
Tabs
to match the legacyTabPanel
componentWhy?
To avoid being overly opinionated,
Tabs
is set up to render a vanillabutton
element, allowing consumers to opt for aButton
component if they wish, via therender
prop.This caused a few styles to be lost, such as the hover color and the alignment of the text on tabs when the tab is wider than its contents.
How?
Add the hover color and necessary layout attributes directly to the default
tab
element.Testing Instructions
flex-grow:1
style to each of theTabs.Tab
components in the Default story (making them wide enough for text alignment to be noticeable)