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

[Bug 12780] New: min, max, low, high and optimum IDL attributes for the meter element should reflect the actual values (of min, max [...] respectively)

From: <bugzilla@jessica.w3.org>
Date: Wed, 25 May 2011 15:33:07 +0000
To: public-html@w3.org
Message-ID: <bug-12780-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12780

           Summary: min, max, low, high and optimum IDL attributes for the
                    meter element should reflect the actual values (of
                    min, max [...] respectively)
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: mounir.lamouri@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Like meter.value actually.

Having all attributes but one reflecting the content attributes seem weird. I
would tend to say that it is preferable to have all attributes sharing the same
logic (here, how they reflect). Given that Presto's and Webkit's implementation
do not follow what the specs currently ask and have .min, .max, .low, .high and
.optimum returning the current value and not the content attribute value, we
should probably change the spec to reflect that.
FWIW, Gecko might implement <meter> IDL attributes reflection the same way.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 25 May 2011 15:33:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:32 GMT