Repository navigation
Make Tabs’ mobile select optional and reactive. - #23
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
Make Tabs’ mobile select optional and reactive
Changes
Tabs now keep their buttons and overflow menu on mobile by default. The new
mobileSelectprop accepts a boolean or reactive ref; setting it totrueenables the native select at viewport widths up to 640px.Changing the prop updates that instance automatically without requiring
refresh(), rebuilding controls, or resetting selection and panel content. Responsive styles now target each Tabs instance’s own controls, preventing a compact parent from overriding nested tabs.The documentation and playground demonstrate the option, including reactive toggling and the new default.
Validation: