FastFind Toobar does not pop up automatically when Find As You Type starts

RESOLVED EXPIRED

Status

()

Toolkit
Find Toolbar
--
major
RESOLVED EXPIRED
13 years ago
9 years ago

People

(Reporter: bytesmythe, Assigned: Blake Ross)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040918 Firefox/0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040918 Firefox/0.10

The FastFind toolbar no longer comes up when I do a "Find As You Type". The only
way to make it appear is to hit Ctrl-F. Even then, it doesn't actually find
anything, as the find previous and find next functions are completely
non-functional.

Reproducible: Always
Steps to Reproduce:
1) Load a webpage containing some text
2) Begin typing to start "Find As You Type"
   (Make sure to use text that appears multiple times in the page)
3) Hit Ctrl-G to find next, or Shift-Ctrl-G to find previous
4) Type some more text which is NOT in the page.
5) Hit Ctrl-F to bring up the FastFind toolbar
6) Enter some text that appears on the page multiple times
7) Verify that the toolbar is doing ANYTHING by clicking the 
   "highlight" button.
8) Click the "find next" and "find previous" buttons
Actual Results:  
First 3 steps:
Typing does not bring up the FastFind toolbar. Typed text is initially found,
but find next and find previous functions do not work from either the keyboard
OR the edit menu.

4th step:
No "text not found" beep

Remaining steps
Toolbar comes up and you can type text in the find field, however matching text
is not selected in the page. The bar is obviously working in some fashion
because clicking "highlight" will turn on and off highlighting in the page. Find
next and previous buttons do nothing at all.


Expected Results:  
First 3 steps:
Beginning "find as you type" should bring up the FastFind toolbar. Using the
find next and previous functions should... well... find the next and previous
occurrences of the search string.

Step 4:
I should hear the "text not found" beep.

Remaining steps:
Toolbar should come up and typed text should be immediately highlighted as it is
found. Find next and previous buttons should find next and previous occurrences
of typed text. (Also, I believe the background of the entry text box is supposed
to change color to indicate whether the text was matched or not. This is not
occurring.)

I thought this might be tied to installing a theme or some extensions, so here
is a list of what I installed:

Theme:
Noia 2.0 Extreme

Extensions:
RadialContext
Linkification
FoxyTunes


I uninstalled the theme and disabled the extensions, but to no avail. Then I
deleted the entire user profile directory and tried again, but still nada.
(Reporter)

Comment 1

13 years ago
I didn't explicitly mention this, but all of the above items DID work when I
initially installed Firefox 1.0PR. I have no idea when they stopped working. I
still suspect some problem with installing either a theme or an extension. I'd
think that if that were the cause then deleting the profile directory should fix
it, but it didn't.

Also, I did check all the related about:config items, and they are set the way
they should be for the features to work properly.

Comment 2

13 years ago
Maybe this is of some help, I get the same problem with FAYT, and I've noticed
all these errors in the JS console:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]" 
nsresult: "0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)"  location: "JS frame
:: chrome://global/content/bindings/browser.xml :: get_fastFind :: line 242" 
data: no]

Also, the FAYT seems to still work fine in the HTML source view.
(Reporter)

Comment 3

13 years ago
Thanks for the info... My javascript console is loaded with the same errors.
Also, the "find next" and "find previous" functions do work in source view,
although I do wish it would use the FindFast toolbar. (There's already a bug
report for that, though.)
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.