12780 2011-05-25 15:33:06 +0000 <meter> min, max, low, high and optimum IDL attributes for the meter element should reflect the actual values (of min, max [...] respectively) 2011-08-17 19:49:00 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 11939 1 mounir ian ian jonas mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 48809 0 mounir 2011-05-25 15:33:06 +0000 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. 53306 1 mike 2011-08-04 05:12:33 +0000 mass-move component to LC1 55331 2 ian 2011-08-17 19:47:15 +0000 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. 55332 3 contributor 2011-08-17 19:49:00 +0000 Checked in as WHATWG revision r6489. Check-in comment: track implementations http://html5.org/tools/web-apps-tracker?from=6488&to=6489