New issue
Advanced search Search tips

Issue 708471 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 577680
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Extreme values within the input date element

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

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to 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 behavior?
Disabling the increment / decrement step when the max / min is reached would be a better indication to the user that the max / min has been reached rather than continuing to extreme max / min values.

- If the min attribute is set but the max is omitted: Disable the decrement step when the min value is reached.

- If the max attribute is set but the min is omitted: Disable the increment step when the max value is reached.

- If the min attribute is set and the max attribute is set: Proceed with the above functionality; or should there be a valid reason for looping: Allow looping of the max / min values.

What went wrong?
- On incrementing the year value with a max attribute set but not min attribute set the year value is set to the extreme value of 0001.

- On decrementing the year value with a min attribute set but not max attribute set the year value is set to the extreme value of 275760.

Did this work before? No 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

This allows the specification "Four or more ASCII digits, representing year..." https://html.spec.whatwg.org/multipage/infrastructure.html#months and provides a normalised user experience.

This relates to the following issues:  Issue #577680  and  Issue #579181 .
See http://html5doctor.com/the-woes-of-date-input/
 

Comment 1 by icis...@gmail.com, Apr 5 2017

Yep this seems like poor user experience in my opinion.

I would expect the value to change when below the min value only if a max value has been defined. Otherwise it should disable the down arrow.
Components: -UI Blink>Forms>Date

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

Mergedinto: 577680
Status: Duplicate (was: Unconfirmed)

Comment 4 by 02wis...@gmail.com, Apr 6 2017

With respect, these issues are both regarding the behaviour of the form field, but this issue proposes a change to the feedback to the user that allows them to know the max / min limit has been reached rather than looping at all.

Sign in to add a comment