163030 - document.captureEvents captures keyboard navigation keypresses.

Status: RESOLVED INVALID

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Scott Johnson]

This page features two text boxes, one above the other.  The first box is in a
form all its own.  If I type text into this box and press enter, the focus moves
to the next box courtesy of the underlying javascript.  I cannot, however, tab
between these two boxes.  While I'm sure this behavior makes sense
programmatically, it makes zero sense from the perspective of the user.  The
user who doesn't view the source simply sees two text boxes.  He puts the cursor
in the first and cannot tab to the second.

Comment 1

[Scott Johnson]

Attachment: possible test case

This file shows two text boxes in table cells very similar to the layout of the
problem page but DOES NOT exhibit the same behavior.

Comment 2

[Malcolm Rowe]

Confirming on 2002080718-trunk (Win32).

Changing summary from:
Can't tab between elements on separate forms
to:
document.captureEvents captures keyboard navigation keypresses.

The referenced page is using document.captureEvents to restrict the characters 
allowed in certain text fields to alphanumeric characters only.  In IE, this 
behaviour works as expected, and TAB still moves between fields.

In Mozilla, *every* non-meta keypress is sent to the document's onkeypress 
handler, including (for example) TAB, F5 (reload), and Alt-Left (back).

This effectively breaks most keyboard navigation.

Most Ctrl and Alt keys work, so Alt-F4, Alt-F, and Ctrl-R all work, but Alt-
Left is disabled, meaning you can't navigate back or forward using the 
keyboard, either.

This can't be right.
-> event handling

Example testcase to follow.

Comment 3

[Malcolm Rowe]

Attachment: Sample testcase

After loading this testcase, you will not be able to TAB between fields, use F5
to reload the page, or Alt-Left to return to this bug report.

Comment 4

[Eric Vaandering (no email)]

*** Bug 148938 has been marked as a duplicate of this bug. ***

Comment 5

[sairuh (rarely reading bugmail)]

->bryner, but punt as needed.

Comment 6

[Scott Johnson]

Is this bug completely dead?  Over 3 years, and it is still marked as NEW?  As stated above in comment #2, this effectively breaks most keyboard navigation.

Comment 7

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

captureEvent has been already dropped.