Closed Bug 303211 Opened 20 years ago Closed 19 years ago

On Slashdot, Tab key gets stuck in a loop so it doesn't go to all links

Categories

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

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: baffclan, Assigned: aaronlev)

References

()

Details

(Keywords: access, regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050802 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050802 Firefox/1.0+ cannot around links keyboard navigation Reproducible: Always Steps to Reproduce: 1. open http://slashdot.org/ 2. down a {Tab](or [Shift]+[Tab])key, around all links 3. login slashdot 4a. down a {Tab] around links headr in a page -> menu's(left tabel) -> story's -> Advertisement's image -> headr in apage -> .... 4b. down a [Shift]+{Tab] around links footer in a page -> slashbox -> tab bar-> url bar -> footer in apage -> .... Actual Results: does not go around all links keyboard navigation Expected Results: go around all links keyboard navigation SerMonkey/2005080205-trunk/WinXP have this problem. Suite 1.7.11/WinXP, Firefox 1.0.4 have not this problem.
Keywords: access, sec508
Summary: cannot around links keyboard navigation → On Slashdot, Tab key gets stuck in a loop so it doesn't go to all links
Keywords: regression
I can reproduce on Fx/Trunk/Linux. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050810 Firefox/1.0+
I can't reproduce the incorrect behavior. Are you both using a Japanese language version of Firefox and might that have an effect?
cannot reproduce with Firefox/2005112006-trunk/WinXP, Seamonkey/2005121110-trunk/WinXP. WFM?
Perhaps my comment 1 was wrong. I can't reporduce with lastest trunk of Firefox and seamonkey. Marking worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.