17990 2012-07-18 07:29:59 +0000 i18n-ISSUE-98: 13 month calendar support 2012-10-01 22:32:36 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX P3 normal Unsorted 1 contributor ian addison ian mike public-i18n-core w3-bugs contributor oldest_to_newest 70441 0 contributor 2012-07-18 07:29:59 +0000 This was was cloned from bug 16966 as part of operation convergence. Originally filed: 2012-05-07 17:32:00 +0000 Original reporter: Addison Phillips <addison@lab126.com> ================================================================================ #0 Addison Phillips 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. ================================================================================ #1 Ian 'Hixie' Hickson 2012-05-10 17:58:57 +0000 -------------------------------------------------------------------------------- What's the use case? ================================================================================ #2 Norbert Lindenberg 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. ================================================================================ 74985 1 ian 2012-10-01 22:32:36 +0000 type=month isn't going to work for that case at all. You're not picking a Gregorian month, you're picking an entirely different kind of time period. The current type=month is for Gregorian months. I would recommend using a pair of <select>s. If this use case is common, then we should consider adding a new control type for months from this calendar. (If you have data showing that this is a common problem, please don't hesitate to reopen this bug.)