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 8387 - The max value should be extended to 24:00 in order to allow time slices like 22:30-24:00 instead of 22:30-23:59 or 22:30-00:00.
Summary: The max value should be extended to 24:00 in order to allow time slices like ...
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:
: 8386 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-26 13:20 UTC by contributor
Modified: 2010-10-04 14:30 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-11-26 13:20:38 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#time-state

Comment:
The max value should be extended to 24:00 in order to allow time slices like 22:30-24:00 instead of 22:30-23:59 or 22:30-00:00.

Posted from: 84.144.55.231
Comment 1 Ms2ger 2009-11-26 17:26:11 UTC 
*** Bug 8386 has been marked as a duplicate of this bug. ***
Comment 2 Ian 'Hixie' Hickson 2010-01-05 11:39:44 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: 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.