[mastermedo]

The shadcn radio button in action: https://ui.shadcn.com/docs/components/radio-group

[rpastuszak]

Protip: the space between the UI control and the label should be done using padding (or achieved via label nesting) so that the entire area is clickable.

    [ x ]   some long label
         ꜛꜛꜛ
         padding here, not margins or gaps

(clicking between the control and the label does nothing now)

[hanspeter]

Calling this a "Protip" is generous.

That the combined element has any surface area that doesn't toggle the radio setting is a straight-up bug.

It is laughable for a component this heavily refined to have such a basic usability flaw.

[tobyhinloopen]

Is this developed by these 10x developers I've heard about?

[efilife]

For some reason it's exceptionally slow for me on chromium. I click and I see it register half a second later. It also has no cursor:pointer which makes it look non-clickable. Is it expected or a bug?

[kaelwd]

Straight up doesn't even register clicks or keyboard focus for me in firefox.

[Sateeshm]

Same in chrome on Android. They work if I switch to Base UI tab and back.

[maelito]

This interactivity definitely adds a wow effect.

[supriyo-biswas]

Is it sarcastic or does it appear only on high frame rate devices? To me it simply feels like another radio button.

[promiseofbeans]

In a hilarious turn of fate, on iOS safari the first time one of the radio options is clicked after loading, the css focus style is applied, but a click is not always registered so the radio item ends up stuck in an invalid weird-looking state. I highly doubt the issue would occur if the built in radio were being used