10767 2010-09-27 12:03:46 +0000 The <progress> and <meter> elements' value IDL attribute should be constrained by the range. Just like with <input type=range>. 2010-10-07 21:07:30 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-progress-element P3 normal --- 1 contributor ian annevk ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 39568 0 contributor 2010-09-27 12:03:46 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-progress-element Comment: The <progress> and <meter> elements' value IDL attribute should be constrained by the range. Just like with <input type=range>. Posted from: 83.85.115.123 by annevk@opera.com 39569 1 annevk 2010-09-27 12:05:18 +0000 Reportedly it already is in WebKit and it will also be that way in Opera. 39570 2 annevk 2010-09-27 12:06:59 +0000 Thanks to Emil Segerås by the way. 39906 3 ian 2010-09-29 07:58:47 +0000 What do you mean by "constrained by the range"? I'm not sure what part of <input type=range> you're referring to here. Can you elaborate? 39909 4 annevk 2010-09-29 08:11:45 +0000 That when you set it, it is constrained by min/max. And when the value content attribute is outside the range the IDL attribute is still constrained on getting. 40278 5 ian 2010-09-30 19:42:17 +0000 Ah, I see. Yeah, I guess that does happen for type=range, since .value returns the /value/ which is constrained. I guess we can do that for <progress> and <meter>... So basically: * progress.value should be changed to return the "current value" (which I should also turn into an xreffed term while I'm at it) on getting and set the content attribute on setting. * meter.value should return the "actual value" (which should also be xreffed) on getting and on setting set the content attribute. Right? 40313 6 annevk 2010-09-30 21:45:59 +0000 Yeah, correct. (I was wrong on how setting should work.) 40805 7 contributor 2010-10-07 20:56:29 +0000 Checked in as WHATWG revision r5591. Check-in comment: Make progress.value clamp to the maximum on getting. http://html5.org/tools/web-apps-tracker?from=5590&to=5591 40806 8 contributor 2010-10-07 21:06:43 +0000 Checked in as WHATWG revision r5592. Check-in comment: Make meter.value clamp to the specified range on getting. http://html5.org/tools/web-apps-tracker?from=5591&to=5592 40807 9 ian 2010-10-07 21:07:30 +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 diffs given above Rationale: Concurred with reporter's comments.