Closed Bug 266497 Opened 20 years ago Closed 20 years ago

Focus doesn't follow "Find as you type" search results

Categories

(Toolkit :: Find Toolbar, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 260041

People

(Reporter: chris, Assigned: p_ch)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

If you use find-as-you-type to find a link in a framed document, the frame where
the text match is found is not in focus when you press ENTER.


Reproducible: Always
Steps to Reproduce:
1. Visit the (framed) Java API URL listed above.
2. Type '/' to invoke find-as-you-type and search for "java.lang" (no quotes).
3. FAYT finds "java.lang" in upper-left-hand frame, press ENTER. This reloads
the lower-left frame.
4. Type '/' to invoke FAYT and search for "String" (no quotes).
5. FAYT finds "String" in lower-left-hand frame. Press ENTER.

Actual Results:  
Link from top-left-hand frame (java.rmi.registry) is loaded.
This is because the last match found in the upper-left-hand frame was "str" from
"registry". The focus appears to remain in the upper-left-hand frame.

Expected Results:  
FAYT found "String" -- the link I was searching for. Pressing ENTER should
follow /that/ link, instead of a previously found link in another frame.


I first noticed this behavior in 1.0 Pre-release (i.e. Firefox 10.x).

Firefox version 0.9 gives the expected result.
Sounds like a find toolbar issue...
Assignee: search → p_ch
Product: Browser → Firefox
QA Contact: firefox.search
(In reply to comment #1)
> Sounds like a find toolbar issue...

Agreed. Can you confirm this behavior?
Component: Search → Find Toolbar / FastFind

*** This bug has been marked as a duplicate of 260041 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.