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 10767 - The <progress> and <meter> elements' value IDL attribute should be constrained by the range. Just like with <input type=range>.
Summary: The <progress> and <meter> elements' value IDL attribute should be constraine...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 12:03 UTC by contributor
Modified: 2010-10-07 21:07 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-09-27 12:03:46 UTC 
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
Comment 1 Anne 2010-09-27 12:05:18 UTC 
Reportedly it already is in WebKit and it will also be that way in Opera.
Comment 2 Anne 2010-09-27 12:06:59 UTC 
Thanks to Emil Segerås by the way.
Comment 3 Ian 'Hixie' Hickson 2010-09-29 07:58:47 UTC 
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?
Comment 4 Anne 2010-09-29 08:11:45 UTC 
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.
Comment 5 Ian 'Hixie' Hickson 2010-09-30 19:42:17 UTC 
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?
Comment 6 Anne 2010-09-30 21:45:59 UTC 
Yeah, correct. (I was wrong on how setting should work.)
Comment 7 contributor 2010-10-07 20:56:29 UTC 
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
Comment 8 contributor 2010-10-07 21:06:43 UTC 
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
Comment 9 Ian 'Hixie' Hickson 2010-10-07 21:07:30 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 diffs given above
Rationale: Concurred with reporter's comments.