- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 05 Jan 2010 11:39:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8387
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-01-05 11:39:44 ---
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: What's wrong with 22:30-00:00? You probably have to support
22:30-01:00 anyway, no? Supporting two ways of giving 00:00 would just lead to
lots of bugs, IMHO.
Note that if this is just a UI issue, nothing is stopping UAs from showing a
24:00 time and submitting it as 00:00.
--
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 Tuesday, 5 January 2010 11:39:46 UTC