Button Group
Locked Segment
A group where the unavailable option explains itself: a padlock, a striped fill and a reason wired to the input through aria-describedby.
What you can change
- the options and their locked flag through options
- the initially selected option through defaultValue
- the reason text through reason and its id through reasonId
A link for your AI agent: preview, code and instructions.
Preview
Use it with AI
- 1. Copy the link.
- 2. Write to your agent in your own words and drop the link into the sentence.
- 3. The agent opens the link and installs the component from the registry.
put this on the home page as the hero:
https://vibeui.ru/c/buttongroup-016?lang=en&theme=dark
Not sure where to paste it? Step-by-step guide
Show the full instructions
What the link says, spelled out. Use it when your agent cannot open links — paste this text instead.
Loading…
For developers
The install command lives in the “Component source” block below — a signed link that stays valid for 24 hours.
Technical notes
The component is self-contained: one file, no dependencies, its own palette in the --vibeui-buttongroup-016-* variables. It is a server component: there are no hooks, and the choice is held by radios inside a fieldset. The locked option gets a real disabled — visual "greying" without it would leave the segment clickable from the keyboard. The reason lies as a paragraph under the group and is tied to the unavailable input through aria-describedby, so it is spoken right after the option name. The unavailability is marked through three channels: pale text, a padlock glyph and a striped fill on a repeating-linear-gradient — opacity alone is not enough for low vision. The borders are collapsed, the rounded corners go to the edge ones only, and hover does not fire on a locked segment thanks to :not(:has(input:disabled)).
Tags
- buttongroup
- disabled
- a11y
- explanation
Component source
The same file your agent installs. Here in case you would rather copy it by hand.
Loading…