Observation on the Tabs Component

Elements
1

@dan @ben I have just started using the Tabs component to create a documentation browser. The component is very powerful and provides a lot of capabilities. Due to the nature of a tab component, it is a little awkward to work with, as you are controlling things from different places.

But my main concern with this component is that it does not lend itself to being turned into a GLOBAL. The primary reason for this is that the TAB LIST cannot be unlinked in a global. Making it impossible to have a global tab component where variable-length TAB LISTS can be used.

This then impacts one’s ability to style the tab component globally. So I have to turn the contents of the tabs into globals to make those consistent, but I then have to manually manage the styling of the tab component.

Is there a reason that the TAB LIST cannot be unlinked to allow the number of tabs to be customized for each instance of a global tab component?

2

Good point, and I’m glad you mentioned it. I noticed the same thing when using the Tabs component, so I’ve put the ideas I had for implementing it on hold for now.

3

I almost did not proceed, but then opted to just do one of the many instances I would need, so I could get a better feel for how it would work. I’m hoping there will be a fix for this problem in the near future so we can fully leverage the Tab component.

4

The Tabs Component uses the “Collection” feature, so unfortunately Global overrides are not supported. However, you can override the content of each tab.

Do remember you can also create custom components to fit your exact needs, especially with the recent improvements in LLM’s…