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 17638 - 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 the Hebrew and Arabic civil calendars. The step function for example is by whole months from January 1970. Wit
Summary: This type assumes a Gregorian calendar. Either this should be explicit called...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-28 18:59 UTC by contributor
Modified: 2012-08-26 03:08 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-06-28 18:59:46 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html
Multipage: http://www.whatwg.org/C#month-state-(type=month)
Complete: http://www.whatwg.org/c#month-state-(type=month)

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 the Hebrew
and Arabic civil calendars. The step function for example is by whole months
from January 1970. Without knowing the calendar type, you cannot validly
return the number of months between January 1970 (Gregorian) and some month in
the Hebrew calendar. The new year starts at a different point in the year, or
sometimes there are 2 Hebrew new years within one Gregorian year. Perhaps an
optional "calendar" attribute on the input tag as well with a list of possible
values like "gregorian" (default), "hebrew", "arabic", and "chinese".

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 contributor 2012-07-18 17:53:28 UTC 
This bug was cloned to create bug 18265 as part of operation convergence.
Comment 2 Ian 'Hixie' Hickson 2012-08-26 03:08:59 UTC 
It is explicitly called out. The section's second paragraph says "The input element represents a control for setting the element's value to a string representing a specific month", where "month" is defined (and the definition linked to by a hyperlink) as "A month consists of a specific proleptic Gregorian date with no time-zone information and no date information beyond a year and a month" along with a reference defining the Gregorian calendar.

I'm happy to consider controls that expose months in other calendars, please file bugs describing the use cases for those controls. (The main use case for type=month is credit card expiry date controls.)