You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment it is only possible to have radios in cvi-radio-group Sass mixin stacked horizontally.
It was requested that consumers of the library should be able to stack radio buttons vertically as well.
What alternatives have you tried?
Perhaps a cvi-track wrapper could be used with cvi-track--direction-vertical modifier class, wrapping the radio buttons. But it is ideal to keep code required for this basic functionality to the minimum.
Does this feature request involve any updates to the reference design?
No, but currently a design for a vertical radio buttons group is missing. We can assume the same gap would be used in the vertical configuration as the currently being used in the horizontal one.
Implementation details
A solution should not represent a breaking change - meaning by default radio buttons should still stack horizontally.
The text was updated successfully, but these errors were encountered:
Summary
At the moment it is only possible to have radios in
cvi-radio-group
Sass mixin stacked horizontally.It was requested that consumers of the library should be able to stack radio buttons vertically as well.
What alternatives have you tried?
Perhaps a
cvi-track
wrapper could be used withcvi-track--direction-vertical
modifier class, wrapping the radio buttons. But it is ideal to keep code required for this basic functionality to the minimum.Does this feature request involve any updates to the reference design?
No, but currently a design for a vertical radio buttons group is missing. We can assume the same gap would be used in the vertical configuration as the currently being used in the horizontal one.
Implementation details
A solution should not represent a breaking change - meaning by default radio buttons should still stack horizontally.
The text was updated successfully, but these errors were encountered: