Hi Thierry,

It would be great if enabled / disabled could also apply to the whole group.

Currently, deactivating the group has no effect. Each button must be disabled.

Hi Vincent,

In VFP, when a container is disabled, user events don't "enter" into it to reach the contained controls. HTML has an opposite behaviour called "bubbling": user events first hit the contained controls then "bubble" up the containment hierarchy up to the document. Any element in the hierarchy can .stopPropagation up.

Note: in the HTML DOM event model API, events are supposed to first go down through a "capture" phase (top-down the containment hierarchy), hit the event target, then enter the "bubbling" phase (bottom-up the containment hierarchy). Because Microsoft IE has not supported the capturing phase until IE 11, web developers have given up the capture mode, eg. jQuery attaches events only in the bubbling phase, and there's no way to use the capturing phase in jQuery.

We could do a sophisticated server-side logic to set and reset each button's disabled attribute based on optionGroup.enabled… However there's a lot of code involved and it'd require extensive testing in both Bootstrap and Classic mode to make sure there's no regression.

Thank you Thierry for this very documented answer, or there is still question of confinement ...

It is not of interest, it is better to deactivate each option.