Re: [whatwg/dom] HTMLFieldsetElements::elements should probably be HTMLFormControlsCollection, too (#871)

I think if these "legacy" interfaces aren't maintained, including fixed where applicable, their use will decline due to limited utility as applications grow in capability, until they're practically dead weight or appendage, and the withering will spread to the entire "HTML forms" specification -- forms will be useless for anything but "legacy" fallback application.

But forms _are_ useful -- without being associated with one controls don't validate properly, with a form you get more or less "automatic" fallback to HTTP processing of form data, etc.

So I am not sure what you are trying to communicate here -- is this the beginning of the end of HTML forms? Are we going to switch over to HTML Web components that re-implement what forms have given us, as many authors have done already? If we can't fix things without breaking old things, are we going to live with slightly broken HTML forms?

Just to mention, a related issue is that elements that are descendants of a `fieldset`  element, are not associated with the form the `fieldset` element is associated with. This is again strange, if not for historic reasons, since a fieldset isn't submittable itself, and effectively then "hides" all controls it contains, from submission or even access through the form itself.

Maybe a DOM version compliance specification by a DOM application (HTML, being one) could help maintain legacy code while allowing new applications to make use of updated interfaces and functionality? Just throwing things out there now, admittedly.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/871#issuecomment-643255745