(In reply to mathieuv from comment #16) > I do think this issue is somehow stucked or forgotten... > > moreover it is labelled as 'enhancement' while users would call it 'bug ' (at least on our helpdesk). > > As for the latest version (113.0), > an `<input type="datetime-local" />` > is still displayed only as a date selector, > there is still no widget for time selector, > > This bug is also referenced in MDM under: https://github.com/mdn/browser-compat-data/issues/16138 > > Is there any news ? Hello mathieuv, Thank you for following up on this bug! From the discussion that we had earlier (comments [#10](#10) and later), the next basic steps are (with updates): 1. Improve a11y of the picker - I am getting back on working on the bug 1802201 (as I just got back from the baby leave this week), it is mostly done but I need to write some tests for it 2. Get UX approval to have it enabled - got it before the leave, but with the UI as is, activated on click/Space anywhere on time sections of the input 3. enable the time picker by default in Nightly 4. get QA to test it in Nightly 5. Let it ride the trains to have it enabled in release For 3-5 I'll check with Emilio and Mike when the a11y patch is landed. As for the updates to the UI such as adding a clock button in the `<input type=time>` to open the time picker or/and embedding it into the date picker for `<input type=datetime-local>`, this would be an enhancement to be implemented later on (not by the Accessibility team, but with us, for sure)
Bug 1726108 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to mathieuv from comment #16) > I do think this issue is somehow stucked or forgotten... > > moreover it is labelled as 'enhancement' while users would call it 'bug ' (at least on our helpdesk). > > As for the latest version (113.0), > an `<input type="datetime-local" />` > is still displayed only as a date selector, > there is still no widget for time selector, > > This bug is also referenced in MDM under: https://github.com/mdn/browser-compat-data/issues/16138 > > Is there any news ? Hello mathieuv, Thank you for following up on this bug! From the discussion that we had earlier (comments [#10](#10) and later), the next basic steps are (with updates): 1. Improve a11y of the picker - I am getting back on working on the bug 1802201 (as I just got back from the baby leave this week), it is mostly done but I need to write some tests for it 2. Get UX approval to have it enabled - got it before the leave, but with the UI as is, activated on click/Space anywhere on time sections of the input 3. enable the time picker by default in Nightly 4. get QA to test it in Nightly 5. Let it ride the trains to have it enabled in release For 3-5 I'll check with Emilio and Mike when the a11y patch is landed. As for the updates to the UI such as [adding a clock button](https://bugzilla.mozilla.org/show_bug.cgi?id=1812669) in the `<input type=time>` to open the time picker or/and embedding it into the date picker for `<input type=datetime-local>`, this would be an enhancement to be implemented later on (not by the Accessibility team, but with us, for sure)