Time picker opened with invalid value changes to another potentially invalid value
Categories
(Toolkit :: UI Widgets, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox153 | --- | fixed |
People
(Reporter: sam, Assigned: sam)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Currently, when the time picker is opened, and the current value is invalid, there is logic to instead select the first item in the picker. However, this does not consider the min value, meaning another potentially invalid time is being selected anyway. When the date picker is in this situation, it displays the closest valid month.
| Assignee | ||
Comment 1•1 month ago
|
||
Currently, when the time picker is opened, and the current value is invalid, there is logic to instead select the first item in the picker. However, this does not consider the min value, meaning another potentially invalid time is being selected anyway. Selecting the minimum valid value instead provides a better experience, and setting it in timeKeeper instead avoids surprise scrolling animations when component state does not match timeKeeper state.
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 3•1 month ago
|
||
| bugherder | ||
Updated•19 days ago
|
Description
•