This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html Multipage: http://www.whatwg.org/C#dom-fieldset-elements Complete: http://www.whatwg.org/c#dom-fieldset-elements Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Consider making HTMLFieldSetElement.elements a plain HTMLCollection Posted from: 87.64.237.177 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20130609 Firefox/24.0
http://logbot.glob.com.au/?c=mozilla%23content#c136004 http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2543
The only difference between the spec and this would be dropping support for setting radio button groups from the fieldset elements list using fieldset.elements.foo.value, right? You'd have to instead do fieldset.form.elements.foo.value, and it would only work if you had a form and the fieldset was all in the form and so on?
Based on IRC conversation, I think the answer to comment 2 is "yes".
Not sure what that logbot link is supposed to show. The live dom viewer tests shows Safari/Chrome use HTMLFormControlsCollection, IE doesn't even have .elements, and Firefox does HTMLCollection. I don't see why we wouldn't want to do the radio button thing in fieldsets. Based on the above, I'm leaning towards WONTFIX. Is there any further information I should consider?
Marking WONTFIX per comment 4; please reopen if you disagree.