Closed Bug 263274 Opened 20 years ago Closed 19 years ago

fastfind doesn't start from the top when a new page loads

Categories

(Toolkit :: Find Toolbar, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: danfriedman, Assigned: bugzilla)

References

()

Details

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

I apologize in advance for the need to few potentially offensive pictures to
reproduce this bug. There is a 'next' link on each page to view the next picture
in the series. Pressing 't' with FastFind enabled will take you to the 'next'
link, pressing enter selects it. When the next page loads, pressing 't' will NOT
find the 'next' link on the new page. It may take 2-3 tries for it to fail, I'm
not sure of the reason for that. It appears the FastFind is not resetting to the
top of the newly loaded page. Hitting ESC and pressing 't' finds the link correctly.

Reproducible: Always
Steps to Reproduce:
1. Go to the url above, or any image on http://themaxx.com/offensive/
2. Press 't' to select 'next', hit 'enter', repeat 2-3 times to see FastFind fail.


Actual Results:  
FastFind reports 'phrase not found'.

Expected Results:  
It should select find the 'next' link as it does on the first page.

This works in every build including the latest of the 0.9 tree. It fails in the
1.0pr and the latest nightly build of the .10 tree.
Version: unspecified → 1.0 Branch
Summary: fastfind fails erroneously → fastfind doesn't start from the top when a new page loads
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
confirmed on 1.0.6 linux, worksforme current trunk and m1.8 branch
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.