Open Bug 367791 Opened 14 years ago Updated 9 years ago

Space may or may not do Page Down depending on how focus is set

Categories

(Firefox :: Keyboard Navigation, defect)

defect
Not set
normal

Tracking

()

People

(Reporter: spam_from_bugzilla, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061205 Iceweasel/2.0.0.1 (Debian-2.0.0.1+dfsg-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061205 Iceweasel/2.0.0.1 (Debian-2.0.0.1+dfsg-1)

I have a div with overflow:scroll.  If I click in the div with the mouse I can then scroll it up and down using PgUp, PgDn, the up/down arrow keys, and the spacebar for page down.

On the other hand, if I set the focus on the div using focus() from Javascript, then spacebar does nothing while the other keys all continue to work.

It seems to me that there must be more than one sort of "focus", since calling focus causes the focus outline border to be shown, while clicking with the mouse doesn't.

I'd love to know if there is something else that I can do from Javascript that gives the "right kind of focus" so that space works.

I'll attach a test case.

Reproducible: Always

Steps to Reproduce:
1. View the test case that I'm about to attach.
2. Press the button.
3. Press PgUp/PgDn/cursor keys - they work.
4. Press space - nothing happens.
5. Reload the test case.
6. Click in the scrolled box with the mouse.
7. Press the keys again.  Now space does work.
Attached file Test case
Following the steps to reproduce, confirmed with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070122 Minefield/3.0a2pre
OS: Linux → All
Hardware: PC → All
Version: unspecified → Trunk
Confirming behavior shown in testcase.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
Behavior shown in testcase still occurs in Firefox 4.0b9

Mozilla/5.0 (X11; FreeBSD i386; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Still here
Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120227 Firefox/13.0a1
You need to log in before you can comment on or make changes to this bug.