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 16966 - i18n-ISSUE-98: 13 month calendar support
Summary: i18n-ISSUE-98: 13 month calendar support
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 enhancement
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2012-05-07 17:32 UTC by Addison Phillips
Modified: 2016-04-18 23:27 UTC (History)
8 users (show)

See Also:


Description Addison Phillips 2012-05-07 17:32:13 UTC Month state

The 'month' type doesn't allow for 13 month calendars (undecimber). The limitation to Gregorian months doesn't work here because you can't convert a month by itself to/from the Gregorian calendar.
Comment 1 Ian 'Hixie' Hickson 2012-05-10 17:58:57 UTC
What's the use case?
Comment 2 Norbert Lindenberg 2012-05-16 02:29:03 UTC
Here's a use case: A web site provides a calendar of events for a synagogue in Israel. The site groups events by month and lets the user pick the month to be displayed using an <input type="month"> element. Being the site of a synagogue, it has selected the Hebrew calendar by using the BCP 47 language tag he-IL-u-ca-hebrew. The Hebrew calendar is a lunisolar calendar with years of 12 or 13 months. This means, the input element needs to be able to handle up to 13 months.
Comment 3 contributor 2012-07-18 07:30:02 UTC
This bug was cloned to create bug 17990 as part of operation convergence.
Comment 4 Travis Leithead [MSFT] 2016-04-18 23:27:24 UTC
HTML5.1 Bugzilla Bug Triage: Incubation needed

Being from a western country, I'm clearly biased on this issue. But I suspect there is need to support valid alternate month and day, or at least User Interfaces that convert from one to another based on lang? (Though this is not possible given just a input[month] type.) Maybe some note in the spec would help here? Suggestions or PRs welcome.

This bug constitutes a request for a new feature of HTML. Our current guidelines, rather than track such requests as bugs or issues, is to create a proposal for the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG ( As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (