Closed Bug 270546 Opened 20 years ago Closed 16 years ago

Find sometimes does not work, although highlighting still does

Categories

(Toolkit :: Find Toolbar, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: iamthebilly, Unassigned)

References

()

Details

Attachments

(2 files)

User-Agent:       -
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

On this page:
http://www.livejournal.com/community/team_tentacle/?skip=35
I searched for the phrase "necrodiac" to locate a certain user's posting. It
would not find it, giving the message "phrase not found" in the bar, but it
WOULD highlight the phrase when 'highlight' was clicked.

Reproducible: Always
Steps to Reproduce:
1. Go To page
2. Type in Phrase
3. Hit "find next" (or just type it in since browser is supposed to jump to it
automatically)

Actual Results:  
find bar says "Phrase not found"

Expected Results:  
Found the phrase
(In reply to comment #0)

Mozilla/5.0 (Windows; U; Windows NT 5.1; pl-PL; rv:1.7.5) Gecko/20041108 Firefox/1.0

I have similar problems, both on the page reported and on other pages. Sometimes
FAYT just does not work. I put an attachment as a proof. Please ask if you need
more information.
*** Bug 279679 has been marked as a duplicate of this bug. ***
I can confirm that this bug occurs on trunk builds.  My build is 20050124.

The bug is intermittent; I have been unable to find a way of reproducing it 100%
of the time.  It does, however, happen often and is a highly annoying bug.
I just discovered how to reproduce this bug 100% of the time.

Steps to Reproduce:
1. Open more than one tab
2. Close a tab
3. Without switching to another tab, do a search in the tab that remained after
you closed a tab.

The summary of this bug should be updated to "Find toolbar fails to find
anything after closing a tab, highlighting still works".

*** This bug has been marked as a duplicate of 274625 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
whups, mistakenly marked as a dup.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Flags: blocking-aviary1.1?
The problem is with opening a new tab and using find as you type.   I have been
able to reproduce with the following procedure:

Open firefox on a Mac Os X machine 2-24-05 nightly.

1) Turn on Find as you type in advanced preferences.

2) Close all windows, but do not quit.

3) File --> Open Location

4) Edit --> Paste:
http://www.hoboken.com/?doc=showclas&pagenbr=2&keyid=1&bed=0&bath=0&lrent=&hrent=&ay=2003&am=0&ad=0

5) hit return : type "sofa" (no quotes)

5a) while the find dialogue is up, click the Highlight button. ((warning: 
workaround.  including this step will fail to reproduce this bug. :warning)only
included as possible step to solving this.)

6) File -->  New Tab

7) Edit  --> Paste:
http://www.hoboken.com/?doc=showclas&pagenbr=2&keyid=1&bed=0&bath=0&lrent=&hrent=&ay=2003&am=0&ad=0

8) hit return :  type "sofa couch" (no quotes)

9) Keep your eye on the word sofa, Click on the first Tab, and Sofa Couch is
briefly selected, and then deselects it's self.  


10)...

11)profit?

Basically once you use find as you type in a new window, no matter how many tabs
you open, find as you type still focuses on the first tab you use it in.

Other workarounds include switching between tabs, or opening a new tab, and then
closing it before using find as you type.


Thank you for fixing it.  I use it all the time.  :) 
Flags: blocking-aviary1.1? → blocking-aviary1.1+
another testcase : http://www.epanorama.net/links/pc_interface.html (contains
javascript). Find toolbar doesn't work most of the times. Highlight works. I get
the following error in JS console:
"Error: uncaught exception: [Exception... "Component returned failure code:
0x80004002 (NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface]"  nsresult:
"0x80004002 (NS_NOINTERFACE)"  location: "JS frame ::
chrome://global/content/findBar.js :: getSelectionControllerForFindToolbar ::
line 210"  data: no]"
Admittedly, the page has a lot of js errors but find should work. I am seeing
the issue with other pages quite frequently. Currently using build FF 20050316
on Win2K, default theme with Adblock, Launchy and Spellbound extensions.
*** Bug 259873 has been marked as a duplicate of this bug. ***
(In reply to comment #9)
> the following error in JS console:
> "Error: uncaught exception: [Exception... "Component returned failure code:
> 0x80004002 (NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface]"  nsresult:
> "0x80004002 (NS_NOINTERFACE)"  location: "JS frame ::
> chrome://global/content/findBar.js :: getSelectionControllerForFindToolbar ::
> line 210"  data: no]"

> Currently using build FF 20050316

Dimitrius, try a more current build.  I believe the checkin for bug 274553 on
20050323 should have solved this problem.  I can't repeat the find issue on the
url you provided with a build from 20050331

Michael, I think you are right. Just tested with FF 20050402 and it is WFM now.
Find works as expected, no js errors for this operation.
please re-nominate if you can reliably reproduce on trunk.
Flags: blocking-aviary1.1+ → blocking-aviary1.1-
*** Bug 269276 has been marked as a duplicate of this bug. ***
*** Bug 275879 has been marked as a duplicate of this bug. ***
*** Bug 289112 has been marked as a duplicate of this bug. ***
OS->All, as duplicates are reported on Linux.
OS: Windows 98 → All
Just downloaded the fresh FireFox 1.0.7 (windows, french) : I'm still
experiencing this bug, may be more than ever, at a point it's very irritating
and blocking.
JS console still shows the same problem (such a surprise) :
Erreur : uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsITypeAheadFind.find]"  nsresult: "0x80004005
(NS_ERROR_FAILURE)"  location: "JS frame :: chrome://global/content/findBar.js
:: find :: line 470"  data: no]

I'm not a specialist to help solve it but I guess that litte bug surely annoyed
many since many many months. Good luck.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5

Have the same problem, reproduced just like comment #5.

After disabling the Greasemonkey extension (ver. 0.6.2) the problem disappears (so it seems). Disabling Greasemonkey itself (not the whole extension) is not enough.

Is this bug encoutnered without Greasemonkey?
*** Bug 318184 has been marked as a duplicate of this bug. ***
Just like Eddie in comment #19, I was able to solve this problem by disabling Greasemonkey (through the extension manager, not by clicking the little monkey).

Judging by previous comments, I think this is a greasemonkey bug.
I doubt this is a greasemonkey problem as suggested in comment #21, because I have the problem and I don't have greasemonkey installed at all.
QA Contact: fast.find
I'm seeing a similar problem in FF2.  Pressing the 'Enter' key will advance to the next occurence, but the Next and Previous buttons have no effect.  A symptom of this problem is that when you switch to another tab and back, the search text in the find toolbar is erased.  Weirder still is that I'm able to open another tab with the same URL and have the Next/Previous buttons work correctly. (Nothing reported in the Error Console.)
I have the same problem whenever I restore a previous session. It does not occur on all sites though (I have the problem at http://api.rubyonrails.org/). Find as you type will find the first occurance, but Find Next does not work. Pressing Enter does find the next match, but not from the quick find bar. First you have to get to the find by, by doing find next or find. Then pressing Enter or shift enter will search forward or backward. If I close the tab, and open a new one to the same site, the problem disappears.
Assignee: bross2 → nobody
At least in these files pressing Next or Previous button have no effect. But for some reason this error does not occure always: http://www.ietf.org/rfc/rfcnnnn.txt  (replace nnnn with any number, e.g. 2779)
Product: Firefox → Toolkit
Is this still an issue in current trunk build?
It seems to work for me right now. I don't know about the trunk build, but it works in:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Ok, thanks for testing. Let's call this worksforme, if this is working correctly in Firefox 3. Please, reopen if someone can still reproduce it there.
Status: NEW → RESOLVED
Closed: 19 years ago16 years ago
Resolution: --- → WORKSFORME
Is the version on this bug trunk only?
What do you mean?
You need to log in before you can comment on or make changes to this bug.