Closed Bug 124567 Opened 23 years ago Closed 20 years ago

"The text you entered was not found" dialog does not close (Find in page)

Categories

(SeaMonkey :: UI Design, defect)

Product:
SeaMonkey
Component:
UI Design
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: marauder, Assigned: bryner)

References

Details

(Keywords: dataloss, regression) 

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8+) Gecko/20011204
BuildID:    20020209

The "The text you entered was not found" dialog does not close whether by mouse
or shortcut.

Reproducible: Always
Steps to Reproduce:
1. ^F
2. search for something not on the current page
3. try to close box

Actual Results:  box doesn't close

Expected Results:  box should have closed
wfm with a 5min old CVS build on win2k

*** Bug 124581 has been marked as a duplicate of this bug. ***
confirming based on the dupe
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Seeing this with build 2002-02-08-21 on Linux.
+dataloss because you can't do anything with mozilla after this happens, only
kill it.
Keywords: dataloss
Adding Find to summary to catch dupes.
Summary: "The text you entered was not found" dialog does not close → "The text you entered was not found" dialog does not close (Find in page)
*** Bug 123179 has been marked as a duplicate of this bug. ***
QA Contact: sairuh → pmac
If you select [File]-[Save Page As] and try to overwrite an existing file,
you are asked "Do you want to replace it?". You can't close this dialog.
0.9.8/Linux doesn't have this bug. Is there any changes after that?
=>bryner
Assignee: trudelle → bryner
*** Bug 124922 has been marked as a duplicate of this bug. ***
*** Bug 127087 has been marked as a duplicate of this bug. ***
This is still in 20020220 daily builds.  Seems like a showstopper
for 0.9.9 on Linux at least.  It pretty much kills the ability
to use the browser if you can't do a Find in Page.
The problem disappered when I removed the Mozilla installation directory and
installed it again cleanly. (I have a script to fetch new nightly builds and it
had been unpacking new versions directly on top of older ones...)

Maybe this was the cause of the bug for other people as well...?
Ditto for me.  Removing ~/mozilla and un-tarring the
mozilla daily build fixed the problem.
*** Bug 127687 has been marked as a duplicate of this bug. ***
So, does anyone still see this bug after a clean re-install?

If not, it should probably be closed as INVALID or WORKSFORME.
Nope, a clean reinstall makes this go away for me.  Thanks
for those who build from cvs, rm dist/{bin,lib} and make again. I think we could
close this bug.
Ok, marking this INVALID. Reopen if necessary.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
*** Bug 129294 has been marked as a duplicate of this bug. ***
*** Bug 130873 has been marked as a duplicate of this bug. ***
*** Bug 131741 has been marked as a duplicate of this bug. ***
8 dups an counting. There is also related bug 130556.
I doubt this bug is invalid.
*** Bug 132923 has been marked as a duplicate of this bug. ***
reopening for investigation. Too many dups to be invalid.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Removing the mozilla (not .mozilla) directory makes this go away.
If having a stale component/chrome registry is the only way to reproduce this,
this becomes more of an installer issue.  pmac (or anyone), can you find any
other ways to cause this to happen?

I just tried with the latest build (last night's) and it works now without any
problem. Don't know what changed.
*** Bug 132096 has been marked as a duplicate of this bug. ***
This seems to have reappeared.

nominating for mozilla1.0.
Keywords: mozilla1.0, regression
OS: FreeBSD → All
*** Bug 130556 has been marked as a duplicate of this bug. ***
I still get this in Linux RC1. It happens even if I delete my .mozilla directory
and start fresh.
Removing .mozilla isn't the solution.  Removing "mozilla/" is the solution; 
wherever you installed that.
*** Bug 138498 has been marked as a duplicate of this bug. ***
*** Bug 146215 has been marked as a duplicate of this bug. ***
I bet ALL of these dupes are due to installing mozilla over an older
version ... I've seen this myself before somebody told me it wasn't
proper to do this
QA Contact: pmac → sairuh
It's probably safe to close this one now.
Reopen if you still see this *after a clean reinstall*.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 20 years ago
Resolution: --- → WORKSFORME
Product: Core → Mozilla Application Suite
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.