W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2011

[Bug 12254] New: Investigate if <progress> element wouldn't need to be form-associated element

From: <bugzilla@jessica.w3.org>
Date: Sun, 06 Mar 2011 10:26:10 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-12254-2486@http.www.w3.org/Bugs/Public/>

           Summary: Investigate if <progress> element wouldn't need to be
                    form-associated element
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: Olli.Pettay@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

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.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 6 March 2011 10:26:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:44 UTC