Issue 579181: input date "year" must be up to 4-digit
Reported by
laukst...@gmail.com,
Jan 19 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36 Steps to reproduce the problem: In order to avoid many issues and user confuse, allow year to up to 4-digit format. Till 9999 will have a enough time to review another standards/conception. What is the expected behavior? What went wrong? Currently: 1. type=date max year 99999 (5-digit) 2. type=month max year 275760 (6-digit) Tests https://output.jsbin.com/kufeva/quiet Did this work before? No Chrome version: 47.0.2526.111 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 20.0 r0 The issue mentioned in Issue #577680 and http://html5doctor.com/the-woes-of-date-input/ , Jan 20 2016
We need to support "four or more digits, representing year" according to the standard. https://html.spec.whatwg.org/multipage/infrastructure.html#valid-month-string Web authors are responsible to limit the maximum date. > 1. type=date max year 99999 (5-digit) No. It must be 275,760. , Jan 20 2016Thanks for pointing to spec, I just open issue for it https://github.com/whatwg/html/issues/539 > Exactly, "Four or more ASCII digits, representing (Gregorian) year, where year > 0", where "or more" has no reason - imagine yourself and your PC in year 9999+ ... it makes no sense. Are you familiar with anybody scheduling its calendar after year 9999+? It adds only new issues and confuse users. Please fix its logic and perhaps the spec. |
||
►
Sign in to add a comment |
||
Comment 1 by brajkumar@chromium.org, Jan 20 2016