Search/Find as you type (FAYT) wraps at first but fails to wrap when repeated



14 years ago
11 years ago


(Reporter: bugzilla.mail, Assigned: aaronlev)



Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a5) Gecko/20041012
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a5) Gecko/20041012

Using "Find as you type" usually wraps. But, if the search is repeated
using either Ctrl/G or F3 (UNIX) in another tab it no longer wraps and
the "The Text you entered was not found" dialogue appears.

Returning to the original tab and hitting Ctrl/G or F3 still fails to

This also fails in mail messages.

Reproducible: Always
Steps to Reproduce:
1. Using 'find as you type' (either for links or text) locate some text
2. Verify that Ctrl/G or F3 repeats the search and the search wraps
3. Go to another tab and hit Ctrl/G or F3, the search no longer wraps
4. Return to the first tab, hit Ctrl/G or F3, the search no longer wraps

It doesn't matter if the text searched for is on the second tab or not,
the search will no longer wrap if you return to the original tab.

Actual Results:  
Repeating a search on a different tab no longer wraps.

Repeating a search once you've failed on another tab no longer wraps
on the original tab.

Expected Results:  
The wrapping should be consistent. If searching wraps it should
continue to wrap.

I suspect there is a conflict between the expected wrapping on FAYT
and the wrap setting in the Ctrl/F find dialogue. In other words, once
FAYT has been 'forgotten' the last FAYT search is now considered the
find dialogue search and the associated wrap settings now apply ... ie
don't wrap.
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:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.