This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12780 - <meter> min, max, low, high and optimum IDL attributes for the meter element should reflect the actual values (of min, max [...] respectively)
Summary: <meter> min, max, low, high and optimum IDL attributes for the meter element ...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11939
  Show dependency tree / graph
 
Reported: 2011-05-25 15:33 UTC by Mounir Lamouri
Modified: 2011-08-17 19:49 UTC (History)
5 users (show)

See Also:

Attachments

Description Mounir Lamouri 2011-05-25 15:33:06 UTC 
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.
Comment 1 Michael[tm] Smith 2011-08-04 05:12:33 UTC 
mass-move component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-17 19:47:15 UTC 
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.
Comment 3 contributor 2011-08-17 19:49:00 UTC 
Checked in as WHATWG revision r6489.
Check-in comment: track implementations
http://html5.org/tools/web-apps-tracker?from=6488&to=6489