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 18267 - This type assumes a Gregorian calendar. Either this should be explicit called out here, or this type should be rethought to be more inclusive of other calendars.The text "midnight UTC on the morning of the parsed date" should be "the midnight UTC that is
Summary: This type assumes a Gregorian calendar. Either this should be explicit called...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 18268 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-07-18 17:53 UTC by contributor
Modified: 2012-09-13 15:31 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2012-07-18 17:53:51 UTC 
This was was cloned from bug 17640 as part of operation convergence.
Originally filed: 2012-06-28 19:13:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-06-28 19:13:53 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html
Multipage: http://www.whatwg.org/C#date-state-(type=date)
Complete: http://www.whatwg.org/c#date-state-(type=date)

Comment:
This type assumes a Gregorian calendar. Either this should be explicit called
out here, or this type should be rethought to be more inclusive of other
calendars.The text "midnight UTC on the morning of the parsed date" should be
"the midnight UTC that is contained within parsed date" because days start at
different times in other calendars.. 

Posted from: 67.180.233.222
User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.52 Safari/536.5
================================================================================
Comment 1 Robin Berjon 2012-09-07 12:38:56 UTC 
*** Bug 18268 has been marked as a duplicate of this bug. ***
Comment 2 Robin Berjon 2012-09-13 15:31:26 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: Accepted
Rationale: As it says in the implementation notes, "Browsers are encouraged to use user interfaces that present dates, times, and numbers according to the conventions of either the locale implied by the input element's language or the user's preferred locale." So it is not only possible to display a UI that is locale aware and can take into account different calendars, converting to the canonical date format (as explained in the Dates section), but actually encouraged.

Of course, implementations might not be entirely up to the par on this just yet, but that's for them to fix by building better UIs.