Closed
Bug 1501987
Opened 7 years ago
Closed 2 years ago
Date input offers to pick dates outside of min and max attributes
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mail, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Steps to reproduce:
1. JSFiddle: https://jsfiddle.net/mLw8ocvg/
2. Click on date field to open the picker.
3. Open the year and month dropdown and select 2019.
4. Click outside of the picker to close it.
Additional STRs:
1. JSFiddle: https://jsfiddle.net/mLw8ocvg/
2. Click on year section of the date field.
3. Press Arrow Key UP.
4. Click outside of the picker to close it.
Actual results:
Date value is 2019-10-26.
Field is marked as invalid with error message "Please select a value that is no later than 2018-10-26".
Expected results:
User cannot pick date after the max date (respectively, date before the min date). I would even advocate to follow Chromium's behavior and prevent users from browsing dates outside of the date range defined by min and max.
| Reporter | ||
Updated•7 years ago
|
Comment 1•7 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0 (20181030100414)
I have tested this report on Windows 10 x64 and Ubuntu 18.04 x64 using the latest Nightly and Firefox release build. I'm able to reproduce the mentioned behavior. When following the steps I'm able to pick a date after the specified max date. However, I see the same behavior in Chrome with the difference that I need to type the date in order to set it to a higher value.
Status: UNCONFIRMED → NEW
status-firefox63:
--- → affected
status-firefox64:
--- → affected
status-firefox65:
--- → affected
Component: Untriaged → Layout: Form Controls
Ever confirmed: true
Product: Firefox → Core
Updated•6 years ago
|
Priority: -- → P3
The first part with choosing a newer unallowed date with the popup input seem to be ok in FF98.
But clicking on the year and Press Arrow Key UP still allows unallowed year selection.
Updated•3 years ago
|
Severity: normal → S3
Comment 4•2 years ago
|
||
Comment 5•2 years ago
•
|
||
Since the bug 1676068 fixed the month-year picker behavior and now the datepicker does not offer an out-of-range month/years, and the input's max/min handling is tracked by the bug 1613280, maybe this bug could be closed now?
Depends on: 1676068
Updated•2 years ago
|
Flags: needinfo?(emilio)
Comment 6•2 years ago
|
||
Yeah the picker behavior which is what this bug was about works now.
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(emilio)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•