1405592 - [Datepicker] min/max constraints not enforced

Status: UNCONFIRMED

(Core :: Layout: Form Controls, defect, P3)

Description

[Massimiliano]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170928135459

Steps to reproduce:

Open datepicker in an input type="date" with "min" and/or "max" attributes set.


Actual results:

The month is displaying correctly the min/max constraints (e.g. days before min and after max are disabled.)
Anyway, after clicking on the month, the month/year switch is ignoring such constraints, displaying every year.


Expected results:

At least the year constraint should be respected. For example, with the following

input type="date" min="2016-01-01" max="2018-12-31"

the year selector should display only 2016, 2017, 2018 years, because it's useless to select any other years (you'll only see a month entirely composed by disabled days)

Comment 1

[Jet Villegas (inactive)]

Jessica: what does the spec say re: this one? Thx!

Comment 2

[Jessica Jong [:jessica] (inactive)]

This is very UI-specific, so the spec does not mention about this. It's correct as long as we set the validity state correctly after the input value is changed.

NI? Scott to see if this is defined in our UX spec.

Comment 3

[Scott Wu [:scottwu]]

Yes this was originally in the UX spec, but we were worried that it might introduce edge cases or usability issues that could affect the feature launch.

I filed bug 1363660 and have a working patch ready for review. If this is a feature that people would like to have, we could ask our UX (:morpheus) to have another look at it.

Comment 4

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals