Inputs don't respect `disabled` prop of containing fieldset

[grncdr]

Inputs don't respect `disabled` prop of containing fieldset

[claviska]

My knee jerk reaction to this is, it's not reasonable for us to try to support this at present. I've spent a ton of time getting form control submission, constraint validation, and form* attributes to work to mimic the platform. To achieve this, we would need to attach mutation observers to each fieldset from every form control. This can get expensive, especially in larger forms.

In fact, looking at the ElementInternals API, I don't immediately see any way to do this even after we switch over. I was curious if this happened automatically — although I wouldn't expect it to — and it doesn't.

https://codepen.io/claviska/pen/mdgewem?editors=1010

This is going to be a wontfix until there's a way to do it without attaching a mutation observer.

[grncdr]

My knee jerk reaction to this is, it's not reasonable ... [snip] ... To achieve this, we would need to attach mutation observers to each fieldset from every form control. This can get expensive, especially in larger forms.

Yeah, I can see how that's not desirable, and the necessary workarounds to preserve any performance do feel pretty unreasonable.

In fact, looking at the ElementInternals API, I don't immediately see any way to do this even after we switch over. I was curious if this happened automatically — although I wouldn't expect it to — and it doesn't.

That's not quite accurate, there is a formDisabledCallback(isDisabled) callback for formAssociated custom elements. See my fork of your codepen here: https://codepen.io/grncdr-the-bashful/pen/XWQmzyX

I think it would be worth revisiting this when Shoelace moves to using ElementInternals and formAssociated (#1706).

[claviska]

Oh, nice! I missed that in the MDN docs. Thanks for the heads up!