16966 2012-05-07 17:32:13 +0000 i18n-ISSUE-98: 13 month calendar support 2016-04-18 23:27:24 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WONTFIX P2 enhancement --- 1 addison robin ian mike public-html-admin public-html-wg-issue-tracking public-i18n-core robin travil w3-bugs public-html-bugzilla oldest_to_newest 67401 0 addison 2012-05-07 17:32:13 +0000 4.10.7.1.9 Month state http://dev.w3.org/html5/spec/single-page.html#month-state-type-month 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. 67576 1 ian 2012-05-10 17:58:57 +0000 What's the use case? 67775 2 w3-bugs 2012-05-16 02:29:03 +0000 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. 70442 3 contributor 2012-07-18 07:30:02 +0000 This bug was cloned to create bug 17990 as part of operation convergence. 125902 4 travil 2016-04-18 23:27:24 +0000 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 (https://www.w3.org/community/wicg/). As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (https://wicg.github.io/admin/intent-to-migrate.html).