1374621 - [DateTimePicker] Time input box with Preset step : Page Up/Down and Home/End keys are not disabled

Status: RESOLVED WONTFIX

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

Description

[roxleitan]

Attachment: Time preset step.html

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170619030208

[Affected versions]:
Nightly 56.0a1

[Affected platforms]:
Windows 10 x 64, Mac OS X 10.12

[Steps to reproduce]:
1.Launch Nightly 56.0a1 with a new profile
2.Open the attached HTML
3.Press Page Up/Down and Home/End keys 

[Expected result]:
Page Up/Down and Home/End keys should become disabled

[Actual result]:
Page Up/Down and Home/End keys are not disabled (can change the time values in the input box)

Comment 1

[Jessica Jong [:jessica] (inactive)]

I think this should be done only if Bug 1301295 is implemented.

Comment 2

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

not breaking usability so it's not a P1.

Comment 3

[Anna Yeddi [:ayeddi]]

It appears to me that the step size should regulate the Up/Down arrow keys, not the PgUp/PgDown and Home/End ones, because the latter ones are moving the selection to a different sets of targets. Home/End should definitely work as they bring the selection to the edges of the value set, but maybe PgUp/PgDown could, for instance, follow the set step size, if it is larger than 5 (as listed in the WAI ARIA spinbutton example: Increases/Decreases the value 5 steps - where 1 step would be set by an author).

Disabling these keyboard shortcuts would reduce the accessibility of the component and would make it more cumbersome for users with limited mobility and/or limited dexterity as well as other keyboard-only users like screen reader users or users of voice control technology to use the time spinbuttons.

:Emilio, maybe this bug could be closed then?

Comment 4

[Emilio Cobos Álvarez [:emilio]]

Yeah, there's various approaches we could take here but disabling them seems unnecessary.