Closed Bug 387993 Opened 18 years ago Closed 18 years ago

possible tab order weirdness for findbar textbox with Fx3.0

Categories

(Toolkit :: Find Toolbar, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 387720

People

(Reporter: mcdavis941.bugs, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007070804 Minefield/3.0a7pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007070804 Minefield/3.0a7pre With Fx2.0, you can tab into the Find Bar's textbox from either direction (i.e., with either Tab from before it or shift-Tab from after it). With Fx3.0a7, this has changed. Now, you can still tab into it, but shift-Tab will skip over it. Not sure if this is a bug but it seems strange. Reproducible: Always Steps to Reproduce: 1. Open Find Bar 2. Search for some term which is found. 3. Click the next button in find bar (so next button receives focus). 4. Shift-Tab once. 5. Notice that shift-tab skipped past the find bar's textbox.
Summary: possible tab order wierdness for findbar textbox with Fx3.0 → possible tab order weirdness for findbar textbox with Fx3.0
Version: unspecified → Trunk
Works for me Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071302 Minefield/3.0a7pre Please try to reproduce with the latest nightly
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071305 Minefield/3.0a7pre This works for me in today's trunk build, but didn't work in a build from 2007-07-11-04. So, I guess this was fixed very very recently. ->WORKSFORME
URL: none
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Actually, it looks like this is a duplicate of bug 387720.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.