16 years ago
13 years ago


(Reporter: timeless, Unassigned)


(Blocks: 1 bug, {testcase})


Firefox Tracking Flags

(Not tracked)



(1 attachment)



16 years ago
[from bug 173542] load the page, press and hold <tab>. you'll get stuck at the ?

Comment 1

16 years ago
Heh - you beat me to submitting this :-)

It seems that Moz doesn't filter out the tab key for the 'onkeypress' event.

Comment 2

16 years ago
-> bryner, focus
Assignee: aaronl → bryner
Blocks: 83552
Component: Accessibility APIs → Keyboard Navigation

Comment 3

16 years ago
Is preventDefault getting set or something?


Mozilla is not getting a chance to use that tab press.

Comment 4

16 years ago
Here are my observations:
in order to make site accessible, both onclick and onkeypress event handlers are
used in an anchor <a> tag:
it seems that Mozilla (rightly or wrongly?) interprets 'tab' key-press as an
pnkeypress event, and thus fires up the associated event. What this means is
that Mozilla gets stuck on this event, and does not tab beyond this event.
<code><a href="/file.html"
onclick="'/file.html','window','etc');return false;"
onkeypress="'/file.html','window','etc');return false;">link

is there an interim workaround for this? (PS! this behaviour was observed in
Mozilla 1.2 and 1.3 on Win2K pc. Have not tested on other os; but have tested in
IE browsers, which work as expected - ie: tabbing does just that; no event
handlers are fired until a key - other than tab - is pressed.
URL is 404.
Created attachment 230574 [details]
Testcase #1
Keywords: testcase
OS: Windows 2000 → All
Assignee: bryner → nobody
QA Contact: dsirnapalli → keyboard.navigation
You need to log in before you can comment on or make changes to this bug.