New issue
Advanced search Search tips
Starred by 10 users

Issue metadata

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



Sign in to add a comment

Setting min value on date input causes year to seemingly overflow

Reported by ian.dev...@gmail.com, Jan 14 2016

Issue description

Chrome Version       : 47.0.2526.111
URLs (if applicable) : http://codepen.io/iandevlin/pen/bErzLE
Other browsers tested:
    Opera: 34.0.2036.47 FAIL
     Safari: n/a
    Firefox: n/a

What steps will reproduce the problem?
1. Navigate to http://codepen.io/iandevlin/pen/bErzLE
(simple contains <input type="date" min="2016-01-14" value="2016-01-14"></input>)
2. Select the year
3. Use the down arrow within the input field to reduce the year value
4. Year value changes to 275760

What is the expected result?
The year value should not be able to be earlier than the year specified in the min datetime value.


What happens instead?
The year value changers to 275760


Please provide any additional information below. Attach a screenshot if
possible.
Incidentally, it works fine if a max datetime value is also set in the input field.

 

Comment 1 by tkent@chromium.org, Jan 15 2016

Labels: Cr-Blink-Forms Cr-Blink-Forms-Date
Owner: tkent@chromium.org
Status: WontFix
This is by design.

Down arrow key at the minimum value cycles the value, it means the maximum value is set.  275760 is the maximum year value which input[type=date] can handle.

Ok, but this does seem a bit odd. Wouldn't it be better UX - and less of a surprise - if the down arrow just didn't go below 2016 in this case?
This feels like a "when engineers do UX" issue. I can't imagine a real-world user encountering a date input like that and not being absolutely confused by suddenly having the year set to 275760...

Comment 4 by laukst...@gmail.com, Jan 19 2016

I just open max year related Issue #415261

Comment 5 by 02wis...@gmail.com, Apr 5 2017

This is not by design; this is by lack of design.

There is no reason why a user would logically choose to cycle through 273,743 years to get to 2017. If there will be no rationality to the logic of the max year then the step down arrow should simply be disabled to inform the user this is the minimum year.

Comment 6 by tkent@chromium.org, Apr 5 2017

 Issue 708471  has been merged into this issue.

Sign in to add a comment