Closed
Bug 185289
Opened 23 years ago
Closed 23 years ago
Hangs indefinitely when using 'find in page' [corrupted XUL.mfl]
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 174473
People
(Reporter: cordet, Assigned: asa)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 5.21; Mac_PowerPC)
Build Identifier: 1.2.1
When I was typing the search string faster than the full dialog box could appear, brought
initial hang and needed to force quit. On subsequent launches w/out reboot, find in page
wouldn't come up at all.
Reproducible: Always
Steps to Reproduce:
1. use quick keys apple+f
2. type before dialog box fully appears
3. watch the spinning beach ball of death
Actual Results:
i eventually had to force quit
Expected Results:
i expected the 'find' feature to work at the same speed as my keyboard/typing, as it was in
the previous built.
Wfm with 2002121308/Win98SE.
Summary: Hangs indefinitely when using 'find in page' → Hangs indefinitely when using 'find in page'
Comment 2•23 years ago
|
||
happens for me too version 1.2.1
previous versions were ok
related to Bug 184876 on Win2k?
please check if deleting the file XUL.mfasl (or XUL.mfl) in your profile
direcoty helps. (Quit mozilla first)
Similar: bug 174473
Comment 4•23 years ago
|
||
I suspect that asking for the find dialog before the page has completely
rendered may also trigger this bug. Eventually I replaced the Application bundle
and then I could use find again. I did not replace anything in the profile
folder. I could not find an XUL.mfl or XUL.mfasl There is a "XUL FastLoad File"
in the profile dir which I have not replaced.
| Reporter | ||
Comment 5•23 years ago
|
||
Deleting the XUL fastload file did the trick!
*** This bug has been marked as a duplicate of 174473 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Summary: Hangs indefinitely when using 'find in page' → Hangs indefinitely when using 'find in page' [corrupted XUL.mfl]
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•