Fix and re-enable the time picker UI
Categories
(Toolkit :: UI Widgets, defect)
Tracking
()
People
(Reporter: emilio, Assigned: sam)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
Attachments
(1 external file)
It was disabled in bug 1315911, presumably needs more work to be enabled by default.
Updated•4 years ago
|
Comment 1•3 years ago
|
||
Accessibility-wise, the datepicker a11y bug 1676068 drastically improves the accessibility of spinner widgets that are included on the timepicker panel, thus it appears to be beneficial to show the timepicker that would, among other pros, communicate to a screen reader user what are the minimum and maximum allowed values for each spin button, etc. (the remaining a11y enhancements for the timepicker panel are tracked in the bug 1802201).
This change (showing the time picker) could increase the adoption of a default time inputs vs custom, rarely accessible ones.
Other browsers like Edge and Chrome (on both macOS and Win) have a timepicker showing by default.
When implemented, the MDN time appearance example may need an updated screenshot as well.
| Assignee | ||
Comment 3•4 months ago
|
||
Hi Emilio! Now that all of the referenced bugs are fixed, did you have anything else in mind that needs to be taken care of before this can be enabled in Nightly? If not, I can put up a patch that flips the pref and fixes up the tests.
| Reporter | ||
Comment 4•4 months ago
|
||
I'm not aware of any other blocker, so yes please, feel free to do so!
And also feel free to send an intent to ship if you want (or if you don't have the cycles lmk and I can do it on your behalf).
Thanks a lot Sam! :)
| Assignee | ||
Comment 5•4 months ago
|
||
Flips the time picker pref now that all known blockers are resolved, and updates existing tests as needed.
Updated•4 months ago
|
| Assignee | ||
Comment 6•4 months ago
|
||
(In reply to Emilio Cobos Álvarez [:emilio] from comment #4)
And also feel free to send an intent to ship if you want (or if you don't have the cycles lmk and I can do it on your behalf).
No problem, I can send one! I have a few questions though after reading through the guidelines. I don't see an existing intent-to-prototype for this, does that mean I should use the intent-to-prototype-and-ship template? Since WHATWG only specifies that input pickers are implementation-defined, what information needs to be provided within the fields for standards and web-platform-tests?
| Reporter | ||
Comment 7•4 months ago
|
||
Yeah, probably worth merging them. And saying that the UI part of this isn't tested by WPT because of that implementation defined stuff is fair enough. The web-exposed details which are already tested by WPT.
| Assignee | ||
Comment 9•4 months ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Adds a time picker UI for <input type="time"> and <input type="datetime-local">, which Blink has had for quite a while, and complements the existing date picker UI.
[Affects Firefox for Android]: No, Android already has a time picker UI.
[Suggested wording]: Added a time picker to <input type="time"> and <input type="datetime-local">, making selecting a time more accessible and intuitive.
[Links (documentation, blog post, etc)]:
Comment 10•4 months ago
|
||
Comment 11•4 months ago
|
||
Backed out for causing failures at test_HTMLSpec.html
Backout link: https://hg.mozilla.org/integration/autoland/rev/9c710513ae62
Failure log: https://treeherder.mozilla.org/logviewer?job_id=573938150&repo=autoland&task=BPTJLb7DTAWqjMQFLWUNQQ.0&lineNumber=3631
Comment 12•4 months ago
|
||
| Assignee | ||
Updated•4 months ago
|
Comment 13•4 months ago
|
||
| Assignee | ||
Updated•4 months ago
|
Comment 15•4 months ago
|
||
Comment 16•4 months ago
|
||
Comment 17•4 months ago
|
||
Backed out for causing wr failures @transform-input-012.html.
Comment 18•4 months ago
|
||
Comment 19•4 months ago
|
||
| bugherder | ||
Updated•4 months ago
|
| Assignee | ||
Updated•4 months ago
|
Updated•3 months ago
|
Description
•