Implement UI for <input type="month">
Categories
(Core :: Layout: Form Controls, enhancement, P3)
Tracking
()
People
(Reporter: scottwu, Unassigned)
References
(Blocks 2 open bugs)
Details
User Story
Try it with: chrome://global/content/testDatePicker.xhtml Currently the architecture is having the MonthPicker as the main component. It creates the Spinner component and provides the properties such as the item it contains, the current item, min/max, and maybe append/prepend generator functions. Once a spinner has a new value, it sends the new state to the MonthPicker, and it will re-render the spinners with new state. Note: currently, rapid scrolling on the year spinner has a bug that could cause it to keep appending/prepending elements.
Attachments
(2 files)
|
20.01 KB,
patch
|
Details | Diff | Splinter Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
|
Reporter | |
Updated•9 years ago
|
|
|
Reporter | |
Comment 1•9 years ago
|
||
|
|
Reporter | |
Updated•9 years ago
|
|
||
Updated•9 years ago
|
|
|
||
Updated•9 years ago
|
|
||
Updated•9 years ago
|
|
|
||
Updated•8 years ago
|
|
||
Updated•5 years ago
|
|
||
Comment 3•4 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:emilio, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Updated•4 years ago
|
|
||
Updated•3 years ago
|
| Comment hidden (advocacy) |
|
|
||
Comment 9•8 months ago
•
|
||
I assume Mozilla's priorities still lie on other features. At least bug 1069609 has a detailed UX specification including month and week pickers. While that spec. is already quite old itself, it seems to lay a good foundation for someone, who wants to implement it.
The main code for the date widget is here:
https://searchfox.org/mozilla-central/rev/43ed185f20ba4d3ef28c78b85102ea88fa63c947/toolkit/content/widgets/datetimebox.js.
Sebastian
|
||
Updated•7 months ago
|
|
||
Comment 10•2 months ago
|
||
maybe consider adding a basic / wireframe version behind a beta feature flag and iterate on it gradually. use AI to help build a basic version; otherwise we might not see any implementation for another decade or two.
|
|
||
Comment 12•2 months ago
|
||
(In reply to kasper from comment #10)
maybe consider adding a basic / wireframe version behind a beta feature flag and iterate on it gradually. use AI to help build a basic version; otherwise we might not see any implementation for another decade or two.
I did actually just create one. I'll try to push it later, so it can be used as a starting point for anyone interested.
Sebastian
|
||
Comment 13•2 months ago
|
||
From what i see in my UI, don't we actually have a month picker in the date picker already (to switch months/years there)? Would already be good if that could serve as a first implementation for a month picker.
|
|
||
Comment 14•2 months ago
|
||
|
|
||
Comment 15•2 months ago
|
||
The WIP patch re-uses the month picker from the date picker as suggested by Robert. For that, the month picker got moved out from datepicker.js into a new monthpicker.js. The field itself already works as expected, though the picker currently stays empty.
So the missing steps are getting the picker to work, let the date picker and month picker share the same markup, adding tests for it, and cleaning up the code. Probably shouldn't be too hard to finish this, though I'm not sure I can get around it soon. So if there's anyone willing to pick this up, feel free to do so!
Sebastian
Description
•