Closed
Bug 290924
Opened 19 years ago
Closed 19 years ago
NS_ERROR_FAILURE in Javascript console when using window.open
Categories
(Thunderbird :: General, defect)
Thunderbird
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 309775
People
(Reporter: Speeddymon, Assigned: mscott)
References
(Blocks 1 open bug, )
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Was modifying a Firefox Extension that works fine in Firefox to run in Thunderbird,the extension uses the javascript window.open command to open a new firefox window/tab to a certain page. When running the extension, clicking on the items in question results in nothing apparently happening, until you look in the javascript console, where this message appears: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMJSWindow.open]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://xmirror/content/xmirror.js :: goTo :: line 2" data: no] the goTo function being referenced just contains window.open(url), and is only used due to the requirements of certain files being expected in an extension. I get a similar error when manually running the window.open() command from within the Javascript console, in fact the only difference is that in place of the goTo near the end, there is <TOP_LEVEL>, and that the command shown in the error is a javascript:window.open instead of being a chrome file reference. But running the alert() command from within the extension OR within the JS Console works just fine, so Im pretty positive that there isnt anything wrong with the extension itself. Reproducible: Always Steps to Reproduce: Download the xmirror extension from update.mozilla.org in the firefox extensions section, modify the install.rdf in the package to allow it to install to the current released thunderbird build, install it in thunderbird, restart thunderbird and open extension manager again. Where it says Select an Extension Mirror, choose any mirror. Close the Extension Manager, and Open the Javascript console. Actual Results: Nothing visibly happened, but an error message was added to the javascript console. Expected Results: Opened a firefox window to the site selected.
Reporter | ||
Updated•19 years ago
|
Summary: Uncaught exception in Javascript console when using window.open → NS_ERROR_FAILURE in Javascript console when using window.open
Comment 1•19 years ago
|
||
Easily to reproduce with current trunk builds when clicking the link of a js warning or error within the js console. It happens for all HW/OS: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMJSWindow.open]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/text.xml :: onxblclick :: line 302" data: no]
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Saw this bug today while using a web calendar. Clicked on an icon to open a pop-up window. There was no visible effect. Looked in the Javascript console, and saw the exact error described in this bug. The error repeated every time until I quit the browser. After I quit the browser, and went back to the same page, the error did not occur. Using Gecko/20050908 Firefox/1.4 Also found that there is bug 177819 describing same error
I just got the same error again today on a diffferent website that uses window.open(). Given that I never saw this until yesterday, I'm guessing that something that changed in Firefox 1.5 is making it show up. Quitting firefox, and going back to same website, the error does not then occur.
(In reply to comment #3) > Given that I never saw this until yesterday, I'm guessing that > something that changed in Firefox 1.5 is making it show up. See Core bug 309775.
Comment 5•19 years ago
|
||
*** This bug has been marked as a duplicate of 309775 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•