7867 2009-10-10 02:12:34 +0000 How should a browser render this? Give examples for "typical" or "good" implementations, maybe even for different device types. Should specify that a desktop browser should give a calendar widget, because airlines etc. want that (implement it in JS, but b 2010-10-12 07:03:43 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#date-state P3 normal LC 1 contributor ian ben.bucksch ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28212 0 contributor 2009-10-10 02:12:34 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#date-state Comment: How should a browser render this? Give examples for "typical" or "good" implementations, maybe even for different device types. Should specify that a desktop browser should give a calendar widget, because airlines etc. want that (implement it in JS, but badly), and it's practical. the user should have the choice both of entering a date in ISO form, in local language notation, and using the calendar widget. Posted from: 78.46.195.14 28614 1 ian 2009-10-20 22:48:31 +0000 I would rather not include sample UI, as it has a tendency to reduce the imagination of implementors. Maybe in a few years when we have an established UI that authors have come to expect, we can add some sample screenshots. 40554 2 ben.bucksch 2010-10-04 15:01:57 +0000 A site that wants to use this needs to know what to expect. Including example and boundaries for size etc.. Without speccing it, a webpage author can only try out all browsers myself - classic example of a bad spec. Also, I don't think an "example" will hinder anybody's imagination much. If I have a good idea, I'll do it. If I don't, I can take your "good" example. 40984 3 ian 2010-10-12 07:03:43 +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: see comment 1.