Closed
Bug 225530
Opened 22 years ago
Closed 22 years ago
"Find in this page" does not work in installer version
Categories
(Firefox :: Installer, defect)
Firefox
Installer
Tracking
()
VERIFIED
FIXED
Firebird0.8
People
(Reporter: paul0286, Assigned: bugs)
References
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031112 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031112 Firebird/0.7+
I click on Edit
I scroll down to FIND ON THIS PAGE
When entering text on the FIND WHAT window, I click on FIND NEXT.
nothing happens
Reproducible: Always
Steps to Reproduce:
1.I click on Edit
2.I scroll down to FIND ON THIS PAGE
3.When entering text on the FIND WHAT window, I click on FIND NEXT.
Nothing happens
Actual Results:
text on the page does not function
Comment 1•22 years ago
|
||
Several people have complained about Find not working in the last few days. Can
you try again with a 11/14 or later build?
Comment 2•22 years ago
|
||
*** Bug 225833 has been marked as a duplicate of this bug. ***
Comment 3•22 years ago
|
||
*** Bug 226084 has been marked as a duplicate of this bug. ***
Comment 5•22 years ago
|
||
I see this with the latest (11-16) windows build on winXP, and the latest Mac
and Linux builds as well.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•22 years ago
|
||
This broke on Nov 15th sometime (I think). It doesn't seem to affect SeaMonkey
at all. Pierre was the main Firebird checker-in on the 15th. This impacts Mac,
Win, and Linux.
OS: Windows XP → All
Hardware: PC → All
Comment 7•22 years ago
|
||
JS Console reports:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.getService]" nsresult: "0x80570018
(NS_ERROR_XPC_BAD_IID)" location: "JS frame ::
chrome://global/content/finddialog.js :: saveFindData :: line 49" data: no]
Updated•22 years ago
|
Summary: In Edit: "find on this page" does not work when entering text. → "Find on this page" does not work
Updated•22 years ago
|
Keywords: regression
Comment 8•22 years ago
|
||
Comment 10•22 years ago
|
||
I substantially rewrote the find in page functionality. That should be fixed,
but please verify.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 11•22 years ago
|
||
Unable to verify as the latest build I can find is Gecko/20031116 Firebird/0.7+
Comment 12•22 years ago
|
||
Justin: you can find unofficial nightlies at
http://www.squarefree.com/burningedge/ or
http://forums.mozillazine.org/viewforum.php?f=23.
Comment 13•22 years ago
|
||
CANNOT verify:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031121
Firebird/0.7+ (03hrs - Mike Tigas (Nova); MNG,DOMi; O2,G6;)
I cannot open "Find in this page..." by choosing the Menu item "Edit". That does
nothing. Only the keyboard shortcut Ctrl-F brings up the dialog.
Comment 14•22 years ago
|
||
That doesn't seem to be the original problem, I think that regressed from
Pierre's fix.
Comment 15•22 years ago
|
||
I just fixed the "Find in Page" and "Find Again" menuitem. Bernd is right, I
introduced this regression.
![]() |
||
Comment 16•22 years ago
|
||
*** Bug 226530 has been marked as a duplicate of this bug. ***
Comment 17•22 years ago
|
||
Still not working for me Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.6b) Gecko/20031121 Firebird/0.7+
Doesn't function through the upper-right text box or the CTRL-F shortcut. Going
Edit>Find in This Page or Find Again doesn't even bring up the dialog.
JS Console error - Error: uncaught exception: [Exception... "Component returned
failure code: 0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.getService]"
nsresult: "0x80570018 (NS_ERROR_XPC_BAD_IID)" location: "JS frame ::
chrome://global/content/finddialog.js :: saveFindData :: line 50" data: no]
Why is the status of this bug RESOLVED FIXED???
Comment 18•22 years ago
|
||
Reopening: two reproductions with today's build (comment 16 and comment 17), one
from the original reporter of this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 19•22 years ago
|
||
Dunno if this is the correct but, but with Gecko/20031121 Firebird/0.7+, when
i use find as you type F3 doesn't work when i wanna continue searching on a
page.
Comment 20•22 years ago
|
||
For me everything works well now.
I can access the dialog via the menu and I can search with it.
thanks pierre
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031123
Firebird/0.7+ (23hrs - Mike Tigas (Nova); MNG,DOMi; O2,G6;)
Comment 21•22 years ago
|
||
"Find in This Page" doesn't work for me either.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031123
Firebird/0.7+
I noticed people saying it was fixed, actually that's why I have waited a while
for a new nightly build testing.
My build was the one with the installer.
I think there are duplicate bugs because the original poster wrote on instead of
in...
Comment 22•22 years ago
|
||
is this bug only happening with the installer build?
Comment 23•22 years ago
|
||
I am using an installer build (20031122) and this does not work.
Comment 24•22 years ago
|
||
what is needed here is to take the same day build without the installer (the zip
file), and see if it works or not.
Comment 25•22 years ago
|
||
This issue appears to be occuring only with the Installer version. Tested using
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031124
Firebird/0.7+
Comment 26•22 years ago
|
||
*** Bug 226674 has been marked as a duplicate of this bug. ***
Comment 27•22 years ago
|
||
-> installer
Assignee: p_ch → bugs
Status: REOPENED → NEW
Component: General → Installer
Updated•22 years ago
|
Summary: "Find on this page" does not work → "Find in this page" does not work in installer version
Comment 28•22 years ago
|
||
This is certainly an 0.8 blocker if we're going to feature the istaller in 0.8.
Setting the TM for ben :-)
Target Milestone: --- → Firebird0.8
Comment 29•22 years ago
|
||
*** Bug 226863 has been marked as a duplicate of this bug. ***
Comment 30•22 years ago
|
||
Still not working with 20031125 build.
Comment 31•22 years ago
|
||
Tested in 20031126 build. While problem is still there, the Up/Down buttons are
visible in W2k Pro now.
Comment 32•22 years ago
|
||
Ben checked in a fix a few minutes ago.
Could someone please verify this with tomorrow's installer build.
Status: NEW → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Comment 33•22 years ago
|
||
I'll be happy to check. Any idea when it will be posted? 20031129 is current
installer posted to ftp site.
Comment 34•22 years ago
|
||
Tested with 20031130 installer (18:02 build) and it WORKS!!
Method:
1 - Installed program and did Ctl-F
2 - Entered "spolsky" for search parameter, with Down chosen. Spolsky found.
3 - Hightlighted some text farther down the page
4 - Entered "spolsky" for search parameter, with Up chosen. Spolsky found.
5 - Repeated Steps 1, 2/4 testing "match case" parameter. Passed tests
6 - Clicked EDIT|FIND IN THIS PAGE, repeated Steps 2/4. Passed tests.
7 - Repeated Steps 1, 2/4 with "mozilla" as search parameter. Found all the
Mozilla entries, and stopped at end or beginning of page
8 - Repeated Step 7 with Wrap chosen. Wrapped as expected.
Comment 36•22 years ago
|
||
Dont know if this is the correct bug to ask about this, but when I do a search
(for example the word "orga" at mozilla.org) with find as you type, I find
something and press F3 (there are no more hits), the status bar will say:
"Text found "orga" - next match"
Shouldnt it say something about that there are not more "orga" words in this page?
Comment 37•22 years ago
|
||
I just tried the F3 function you mentioned, and it stops at the bottom of
20031130 build, which is the version I tested the bug in for Simon.
Double-check your build in HELP|About Mozilla Firebird. There will be a build
date in there.
Comment 38•22 years ago
|
||
Sorry, I wasnt clear in my last comment. I meant http://bugzilla.mozilla.org/
1. use find as you type and type in "orga", the beginning of the word
organization will be selected.
2. Now press F3, there are no more matches, I would expect to see "no more
matches" or whatever, instead I now see
"Text found "orga" - next match"
Which I find to be confusing, and if i remember correct this wasnt like this
before. Using build 20031201.
Updated•19 years ago
|
QA Contact: bugzilla → installer
You need to log in
before you can comment on or make changes to this bug.
Description
•