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 7867 - 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
Summary: How should a browser render this? Give examples for "typical" or "good" imple...
Status: RESOLVED WONTFIX
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: LC
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: 2009-10-10 02:12 UTC by contributor
Modified: 2010-10-12 07:03 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2009-10-10 02:12:34 UTC
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
Comment 1 Ian 'Hixie' Hickson 2009-10-20 22:48:31 UTC
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.
Comment 2 Ben Bucksch 2010-10-04 15:01:57 UTC
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.
Comment 3 Ian 'Hixie' Hickson 2010-10-12 07:03:43 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: Rejected
Change Description: no spec change
Rationale: see comment 1.