[Segmented button] Add disabled state per button element?

[sandra-post]

✨ Is your feature request related to a problem? Please describe it.

In the Release Q&A, we have been asked by an internal project whether its possible to add the additional state "disabled" to the segmented button, because its not available on the segmented button.

Their use case:

🔄 Describe alternatives you've considered

Theoretically, the segmented button is intended to be used to switch views, and as single select. We have the component [base] Button group #106 in the backlog which would be intended for this use case.

--> To add disabled state to segmented button or implement it as planned in the Button group component?

[leagrdv]

To further discuss:
We need to align dev and design, as "Segmented button" is used as a navigation element in design but it has been implemented as a form element in dev (which could therefore be disabled). Should we update implementation and make it a navigation element (then it would be another version of the tabs?), or keep implementation as is and update design usage to be within forms?

[leagrdv]

Answer to the project: If they want to use the segmented button this way, they should update disabled state (no dotted line, strikethrough on text). Button group is coming in the near future for this use case.

[rouvenpost]

Feedback from the Meeting: Houssam already switched to the Button Group and sytled it for V2.
The Project also uses a Tiny Version of the Button Group wich they developed themselfs. It Looks good and we should keep in Mind that we have to provide a Tiny Version when we tackle the Button Group for V2.