fixed nested tabs orientations #2469
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rroyb
requested review from
mayank99 and
r100-stack
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Fixes #2423.
When nesting
Tabscomponents, there were orientation and spacing issues. For instance, as described in the issue above, nesting a horizontally oriented tab component within a vertically oriented tab component resulted in both being vertically oriented.This PR addresses the incorrect orientations of nested
Tabscomponents and related styling/spacing issues.Testing
Manually tested using Chrome Dev Tools and the sandbox.
Docs
Added changesets