Closed
Bug 90130
Opened 24 years ago
Closed 24 years ago
uncaught exception in finddialog.js and findUtils.js when searching in frameset document
Categories
(SeaMonkey :: Search, defect, P4)
SeaMonkey
Search
Tracking
(Not tracked)
VERIFIED
WORKSFORME
Future
People
(Reporter: bugzilla, Assigned: samir_bugzilla)
References
()
Details
(Keywords: helpwanted)
If you go to:
http://gemal.dk/test/mc.html
and press Find is this Document and enter a search string and press Ok you get:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIWebBrowserFind.findNext]" nsresult:
"0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
chrome://global/content/finddialog.js :: onOK :: line 117" data: no]
build 20010709 on win2k
| Reporter | ||
Comment 1•24 years ago
|
||
If you afterwards press Find Again you get:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIWebBrowserFind.findNext]" nsresult:
"0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
chrome://communicator/content/findUtils.js :: findAgainInPage :: line 76" data: no]
Summary: uncaught exception in finddialog.js when searching in frameset document → uncaught exception in finddialog.js and findUtils.js when searching in frameset document
Comment 2•24 years ago
|
||
Henrik,
Would you have time to come up with patches for all these search-related js
strict-mode warnings? I can check them in for you. Thanks.
~Samir
Assignee: matt → sgehani
Priority: -- → P4
Target Milestone: --- → mozilla0.9.5
| Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.5 → Future
| Assignee | ||
Updated•24 years ago
|
Keywords: helpwanted
| Reporter | ||
Comment 3•24 years ago
|
||
not sure what I had in mc.html but it's gone now...:(
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•