This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 13657 as part of operation convergence. Originally filed: 2011-08-04 02:16:00 +0000 Original reporter: Cynthia Shelly <cyns@microsoft.com> ================================================================================ #0 Cynthia Shelly 2011-08-04 02:16:55 +0000 -------------------------------------------------------------------------------- Range says that the exact number is not important, but it renders as a slider. There are sliders where the exact number is important. The user agent could pick which one to display based on the dimensions given in the style sheet. This would allow it to maintain the same resolution for the tick marks, despite the differences in width. This is very vague. These different presentations should be controlled with CSS, not the browser. ================================================================================ #2 Anne 2011-08-14 13:58:50 +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: Rejected Change Description: no spec change Rationale: It is not clear what needs to be done here. If you want an exact number, use type=number. The specification does include broad UI suggestions, to aid implementors, but does indeed not specify UI in detail because we do not want to constrain implementations. This is all by design. ================================================================================ #3 Cynthia Shelly 2011-12-16 21:45:00 +0000 -------------------------------------------------------------------------------- So, I think that just removing the clause "but with the caveat that the exact value is not important" would make it less confusing. consider the scenario where I have a slider with 50 at one end and 100 at the other, and 4 tick marks in between, and step of 10. In that case, the range does represent a set of specific numbers. This is a pretty common design pattern for sliders on desktop apps. The sentence above makes it sound like Range is not the right control for this. If range is not the right control for this, what is? ================================================================================ #4 Anne 2011-12-17 01:22:24 +0000 -------------------------------------------------------------------------------- Sounds reasonable to me. ================================================================================ #5 Ian 'Hixie' Hickson 2012-02-01 00:21:03 +0000 -------------------------------------------------------------------------------- The right control for that is type=number, as far as I can tell. If you use a slider, the user can't see the number, so obviously the number can't be important. ================================================================================ #6 contributor@whatwg.org 2012-07-18 04:37:45 +0000 -------------------------------------------------------------------------------- This bug was cloned to create bug 17801 as part of operation convergence. ================================================================================
*** Bug 17801 has been marked as a duplicate of this bug. ***
I stand by point 5.