Closed
Bug 370031
Opened 18 years ago
Closed 15 years ago
Cycling through tabindex among HTML inputs only works once
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: WeirdAl, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, testcase)
Attachments
(1 file)
(deleted),
application/xhtml+xml
|
Details |
I discovered this while testing a fix for bug 306058. Steps to reproduce: (1) Tab all the way through the document. (2) Tab past the URL bar and search bar in the main window. (3) Tab until you land in another HTML input. Expected results: You should land in the third HTML input (index 1). Actual results: You land in the first HTML input (no index). requresting blocking1.9: This is actually an accessibility issue, because the next tab doesn't take you to another HTML input - but instead out of the document altogether.
Flags: blocking1.9?
Reporter | ||
Comment 1•18 years ago
|
||
also seen on Mac trunk build. OS, Platform -> All.
OS: Windows XP → All
Hardware: PC → All
Comment 2•18 years ago
|
||
If I click the document with the mouse, then focus the URL bar with Control+L and go tabbing through the document, it jumps the index 1 and follow the rest of the order.
Reporter | ||
Comment 3•18 years ago
|
||
In nsEventStateManager::GetNextTabbableContent, the stacks are identical; the only difference I can find is that the first time this method gets called, aStartFrame is null and aIgnoreTabIndex is false. The second time, aStartFrame is not null and aIgnoreTabIndex is true.
Comment 4•18 years ago
|
||
Sorry... it depends where you click. Index 2 is the easier to reach, since the whole area bellow it will activate it.
Flags: blocking1.9? → blocking1.9-
Whiteboard: [wanted-1.9]
Updated•17 years ago
|
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
Updated•15 years ago
|
Comment 5•15 years ago
|
||
Fixed by bug 178324.
I can still reproduce with: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.5pre) Gecko/20091009 SeaMonkey/2.0pre
Comment 7•14 years ago
|
||
(In reply to comment #6) > I can still reproduce with: > Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.5pre) Gecko/20091009 > SeaMonkey/2.0pre How about a current version or trunk?
Eh, yeah. Sorry. My fault. I thought that that SeaMonkey version was using trunk.
You need to log in
before you can comment on or make changes to this bug.
Description
•