This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Apparently <progress> element is "form-associated" just because of label, but what useful feature does the .form attribute bring in? <progress> isn't submittable, nor resettable, and not even "listed element", so it doesn't show up in form.elements. There is just .form in the progress element, but from that .form you can't even get back to progress. Quite strange. <meter> has similar problem.
Perhaps "Labelable elements" should be changed so that they don't need to be "form-associated"
Another possibility, in which case having progress/meter form-associated makes more sense, would be to make them resettable. That would make them work closer to output. In a way progress/meter are different kinds of representations of some abstract output.
Since progress/meter are not submitted as part of the form I think that removing .form makes the most sense.
(In reply to comment #3) > Since progress/meter are not submitted as part of the form I think that > removing .form makes the most sense. What about the output element then?
I just modeled <progress> and <meter> after <label>, which is form-associated in the same (somewhat pointless) way. I can't really think of any reason that labelable elements should be form-associated, so if nobody has a desire to keep them form-associated (e.g. because it would make implementing it harder), I would be fine with changing the 'labelable' category to be a separate concept from 'form-associated'.
(In reply to comment #5) > I just modeled <progress> and <meter> after <label>, which is form-associated > in the same (somewhat pointless) way. I can't really think of any reason that > labelable elements should be form-associated, so if nobody has a desire to keep > them form-associated (e.g. because it would make implementing it harder), I > would be fine with changing the 'labelable' category to be a separate concept > from 'form-associated'. I don't see any reason to keep <meter> and <progress> as form-associated elements because they are labelable elements. If making them resettable is out of consideration, I don't see any strong reason to keep them form-associated.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r6221. Check-in comment: Remove <progress form> and <meter form> since they are basically useless. http://html5.org/tools/web-apps-tracker?from=6220&to=6221
mass-move component to LC1