[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|NEW                         |RESOLVED
         Resolution|                            |NEEDSINFO




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-06 04:47:34 ---
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: Did Not Understand Request
Change Description: no spec change
Rationale: Could you describe the use case for this? Why would the UI allow
more or less granularity than the submission format includes? Surely throwing
away user data is a bad idea, and if the user didn't provide the data, we can't
submit it. Doesn't this argue that they should be the same?


-- 
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 Wednesday, 6 January 2010 04:47:36 UTC