Replies: 1 comment 1 reply
-
Thanks for creating the discussion. Tabs doesn't really support having interactive elements inside at the moment (it would interfere with keyboard navigation). I think this would be a good feature to support, but I don't think we have an issue tracking this at the moment. I think the implementation would probably look similar to TagGroup, which also happens to have an |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First, thank you for all the hard work you put into building such a polished and accessible component library, it’s been invaluable to our projects.
I’d like to suggest a potential enhancement for the component:
Currently, there’s no built-in way to detect when a user closes or removes a tab—for instance, when using scroll buttons or clicking a close icon. It would be really helpful to have an optional onClose callback prop on the (or perhaps on or each ), which could be invoked whenever a tab is programmatically or interactively closed.
This is the design I have:
Beta Was this translation helpful? Give feedback.
All reactions