17640 2012-06-28 19:13:53 +0000 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 2012-07-27 09:41:11 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#date-state-(type=date) P3 normal Unsorted 1 contributor ian edwin_hoogerbeets ian mike contributor oldest_to_newest 69512 0 contributor 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 71001 1 contributor 2012-07-18 17:53:54 +0000 This bug was cloned to create bug 18267 as part of operation convergence. 71561 2 ian 2012-07-27 02:09:05 +0000 Is this bug asking about the UI or the wire format? 71599 3 edwin_hoogerbeets 2012-07-27 09:41:11 +0000 For the UI. I think for an actually useful input field of type "datetime", the user should be able to enter dates in different date/time formats depending on their locale or the locale of the web page. This format will need to be converted to the standard global date and time format (that's what you mean by "wire format", right?) before being sent to the web server. But, as far as I can tell from the standard, you had intended that anything the user can type into this type of input field can only be a specific format of the Gregorian calendar. That is, I cannot type "24 Tammuz 5772" or "5772-04-24" and have the browser recognize the date in the Hebrew calendar and convert it to the equivalent Gregorian global date and time value and submit that to the web server. (Though as an i18n guy, I'd love to be able to specify the attribute calendar="hebrew" and have behave that way!) So all I'm saying with this bug is that the description in this section of the standard should be explicit that this value is intended to be Gregorian date/times only. (This is already hinted in the green comment text underneath it.)