573411 - scrolling with page up and page down doesn't work correctly after clicking on a select dropdown

Status: NEW

(Core :: Layout: Form Controls, defect)

Description

[philippe (part-time)]

Attachment: test case

STR:
1. *click* with the mouse on a select dropdown, choose an option
2. use page up or page down keys to scroll the page

AR: the options in the select are scrolled (to the 1st or last one)
ER: scroll the page up or down

The expected behaviour is what Safari does (as far back as Safari 1.3 on OS X 10.3.9). This never worked correctly with Gecko browsers.

Comment 1

[Boris Zbarsky [:bzbarsky]]

This is by-design, to allow keyboard navigation inside the <select>.  Note that the up/down keys also change the selected option, right?

Whereas in Safari, the behavior is inconsistent.  Up/down make the dropdown appear, while other keyboard navigation operates on some totally different object.  I really don't think we want the Safari behavior here.

Comment 2

[philippe (part-time)]

In Safari 5, 10.6.4, the page up / page down keys only affect the select options when the pop-up is visible.

Alternate STR
1. load testcase
2. 'tab' to select (the select is focussed in both Gecko and WebKit)
3. press page down
--> gecko: the options change
--> safari: page scrolls down

after step 2, in safari:
a. press spacebar --> the options pop-up pops up. 
b. press page down --> the last option is selected.
c. press enter to accept the selection (and dismiss the pop-up)
d. press page down --> page scrolls

Comment 3

[Boris Zbarsky [:bzbarsky]]

Right, I know what Safari's behavior is.  The point is that they hijack some but not all scrolling navigation keys.  That leads to inconsistent and confusing behavior (why does pageup work while up doesn't?)  We try to keep the behavior consistent.

Comment 4

[philippe (part-time)]

Because the primary function of the arrow keys (up/down) is to affect the selection (in lists), not to navigate the page
http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/XHIGUserInput/XHIGUserInput.html#//apple_ref/doc/uid/TP30000361-TPXREF13

Safari behaviour is consistent with the behaviour of the OS

Comment 5

[Boris Zbarsky [:bzbarsky]]

Sounds like a UI design issue, then (deciding whether cross-platform consistency or OS-consistency is more important here).