1363660 - [DateTimePicker] Disable month and year spinner items that are outside of min/max range

Status: NEW

(Core :: Layout: Form Controls, enhancement, P3)

Description

[Scott Wu [:scottwu]]

For years and months that are out of the min/max range, we could disabled them in the spinners.

Though originally in the UX spec, it has been de-scoped in favour of a more simplified UI for now. This is to avoid unforeseen edge cases that could become blockers.

If you think whether this feature is a good idea or not, or if you can think of cases that could break this feature, please let us know.

Comment 1

[Scott Wu [:scottwu]]

Attachment: Bug 1363660 - Disable out of range months and years

Review commit: https://reviewboard.mozilla.org/r/137880/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/137880/

Comment 2

[Scott Wu [:scottwu]]

Comment on attachment 8866255 [details]
Bug 1363660 - Disable out of range months and years

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/137880/diff/1-2/

Comment 3

[luudde]

Hi! This enhancement would solve a rather weird user experience when using ISO-dates.

Assume I enter an empty date-field with yyyy-mm-dd. I now type my date 20191002. The field now says "201910-02-dd" because 201910 is a valid year.

Now assume I enter the empty date-field again. Now I know I need to use tab to jump between fields. I type "2019 TAB 10 TAB 02". Surprisingly, I have now left the datefield and typed 02 into the next field. This happens because once I had typed the mm-part "10" I was automatically put in the dd-part, and tabbing made me leave it. So the current workflow for ISO-dates is "yyyy TAB mm dd". Chromium works in the same way so far.

Setting max="9999-12-31" should reasonably constrain the values accepted into the form in the first place and enable typing "yyyy mm dd" without tabs altogether. Chromium behaves like this.

I don't know if this is the right place for this. Rather than having my comment die here, if you read this and realize it's in the wrong place, feel free to reach out to me with any input on where to move with this.

(Another suggestion would be to implicitly default the max-value, because users seldom plan beyond the year 9999, but that's for some specification far far away.)

Comment 4

[Daniel Holbert [:dholbert]]

I think bug 1613280 basically covers the issue described in comment 3.