Indeed the button text should not be selectable
i am using similar CSS

but why only for radio buttons and not for all buttons ?
i mean why not at the .btn class ?

<button> elements prevent selection for their nature, and they don't need that style.
However, Bootstrap 4 sets the stile user-select: none; to .btn class, as you suggested.

In this case, I just wanted to limit this style to the barely necessary, that is the Label we use to simulate the Button Group.
This way I'm pretty sure that this modification won't impact any general use of the class .btn by third party extensions.
So yes, I confirm my preference to keep this style under the button group element only.

I have tested this item ✅ successfully on 9c396ff

the text inside the radio buttons should not be selectable

hm, why?

the text inside the radio buttons should not be selectable
hm, why?

hhmm, because it feels like it is not a button, right ?
Bootstrap 4 does it not only to radio buttons but to all

However, Bootstrap 4 sets the stile user-select: none; to .btn class, as you suggested.

hhmm, because it feels like it is not a button, right ?
Bootstrap 4 does it not only to radio buttons but to all

hm why? I do not see the problem at all.
It is a good to be able to select the text (no mater it is fake button, link, simple text block), to copy to someone/somewhere.
That buttons not selectable, it just because browser did not made them selectable for now,

In the past the links also was not selectable, but now they are selectable.

I am not against this PR, but I do not see a reason why we need to do this random stuff ?

My opinion

Having it selectable will be mostly useful to programmers and not to the average user, for whom it is a kind of weird / annoying compared to what user is used to in regards of buttons, and also maybe a little confusing

and anyway the programmers can just inspect the element and copy the text

okay, I was just curious, thought maybe there some serious reason for it ?

@Fedik At personal level, I have nothing against the fact to select text inside radio buttons, but it's not about our personal opinions. It's a matter of User Experience instead.

1. Consistent user interface. What should a user think when he realises that some buttons (actual buttons) does not allow text selections, while others (radio buttons) do allow it? It simply gives a feeling of overall poor quality.
2. Enforce Bootstrap guidelines. Since Joomla default templates are Bootstrap based, and Bootstrap's trend is clearly in that direction, it is fair to follow that behaviour.
3. Avoid weird and unfamiliar behaviour. Currently the action of selecting text only, also causes the button becomes active, and vice versa one imprecise button click may cause an unwanted text selection. I can't remember any other user interface that makes something like that. This confuses and bothers the user.

Maybe someone from the former User Experience Team (JUX) may confirm?

I have tested this item ✅ successfully on 9c396ff

Ready to Commit after two successful tests.

I have tested this item ✅ successfully on 9c396ff

Values change on click, text is not selectable, and values are saved properly
Tested with frontend protostar template, backend isis template

Merged thanks!