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 10122 - re: resolving a step mismatch, it would be good to state that if two values are equally near to round up
Summary: re: resolving a step mismatch, it would be good to state that if two values a...
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-07-09 15:38 UTC by contributor
Modified: 2010-10-04 14:32 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-09 15:38:30 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#range-state

Comment:
re: resolving a step mismatch, it would be good to state that if two values
are equally near to round up

Posted from: 222.147.252.201 by w3.org@boblet.net
Comment 1 Oli Studholme 2010-07-09 15:42:03 UTC 
Based on input type=range min=100 max=130 step=10 Webkit browsers round to 120. It would be good to mention rounding up in the spec so this is consistent

Ref:
http://krijnhoetmer.nl/irc-logs/whatwg/20100709#l-916 start of discussion
http://krijnhoetmer.nl/irc-logs/whatwg/20100709#l-943 foolip suggesting this
Comment 2 Oli Studholme 2010-07-09 15:48:56 UTC 
PS raspberries to brucel for making me file this PFFFT!
Comment 3 Ian 'Hixie' Hickson 2010-08-30 18:37:57 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 4 contributor 2010-08-30 18:38:51 UTC 
Checked in as WHATWG revision r5400.
Check-in comment: Make type=range round up when it's ambiguous
http://html5.org/tools/web-apps-tracker?from=5399&to=5400