New issue
Advanced search Search tips
Starred by 2 users

Issue metadata

Status: WontFix
Closed: Jan 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Sign in to add a comment

Issue 579181: input date "year" must be up to 4-digit

Reported by, Jan 19 2016

Issue description

UserAgent: 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?
1. type=date max year 99999 (5-digit)
2. type=month max year 275760 (6-digit)


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

Comment 1 by, Jan 20 2016

As per  issue 577680  adding tkent for more updates.

tkent@ - Observed there was a recent issue closed by you, Both the issue looks similar. Could you please look in to it, else feel free to re-assign it to the right owner.


Comment 2 by, Jan 20 2016

Labels: -Cr-UI -OS-Windows -Arch-x86_64 Cr-Blink-Forms Cr-Blink-Forms-Date
Status: WontFix
We need to support "four or more digits, representing year" according to the standard.

Web authors are responsible to limit the maximum date.

> 1. type=date max year 99999 (5-digit)

No. It must be 275,760.

Comment 3 by, Jan 20 2016

Thanks for pointing to spec, I just open issue for it

> 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.

Comment 4 Deleted

Sign in to add a comment