- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 21 Oct 2009 23:19:33 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7868 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NEEDSINFO |WONTFIX --- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2009-10-21 23:19:33 --- (In reply to comment #10) > Any calendar, reminder, booking etc. site. I looked at a bunch, and I couldn't find any sites that asked for a date only (no time) and yet used the 24-hour period corresponding to the user's submission time zone, and not the date irrespective of time zone. Could you provide a URL to one explicitly that I could look at? > > as opposed to at the time of display > > The problem may be that you think of a date as a string (to display). It's not. > It has a *meaning*. A date is a point (or range) in time, and may be acted upon > by the site/server. Please go back to comment 5 and think through it from the > perspective of the server programmer. I understand that the date has meaning. I just don't think sites are doing what you think they're doing. I think the use case for a date control doesn't need a time zone in practice. For example, Google Calendar uses a date control only for events that are time-zone agnostic — if I set an event to be on Thursday October 22nd 2009 while my time zone is UTC+12, and then change my time zone to UTC-12, the event still claims to be on Thursday, even though there are no minutes in common for those two events. For timezone-dependent events, sites have date+time controls, which is type=datetime. 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: I do not believe the use cases match what you describe. -- 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, 21 October 2009 23:19:34 UTC