[Bug 8436] "granularity that is expected (and required) of the value, by limiting the allowed values" -- granularity requirments may often be different for validation versus usability/ui-control purposes. There should be a 'step' for possible GUI controls and an oth

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8436


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-06 00:34:53 ---
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:

In most user interfaces, the user can just type in the new value, they don't
have to use the button. But in general, I think this is a UI issue — there's no
reason the UI's buttons have to follow step=""'s value, they can be adjusted
dynamically or be based on whether the user is holding a shift key, or whatnot.
So I think we should let the browsers figure this out for now. If it turns out
they need something, then we can add it later.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 6 February 2010 00:34:56 UTC