Closed
Bug 539579
Opened 15 years ago
Closed 7 years ago
uncaught exception: [Exception... "The container of an boundary-point of a range is being set to either a node of an invalid type or a node with an ancestor of an invalid type." code: "2" nsresult: "0x805c0002 (NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: miroslav159, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; cs; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTBDFff GTB7.0 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; cs; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTBDFff GTB7.0 (.NET CLR 3.5.30729)
Chyba: uncaught exception: [Exception... "The container of an boundary-point of a range is being set to either a node of an invalid type or a node with an ancestor of an invalid type." code: "2" nsresult: "0x805c0002 (NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE_ERR)" location: "chrome://google-toolbar-lib/content/toolbar.js Line: 2239"]
Reproducible: Always
Actual Results:
Chyba: uncaught exception: [Exception... "The container of an boundary-point of a range is being set to either a node of an invalid type or a node with an ancestor of an invalid type." code: "2" nsresult: "0x805c0002 (NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE_ERR)" location: "chrome://google-toolbar-lib/content/toolbar.js Line: 2239"]
Expected Results:
Chyba: uncaught exception: [Exception... "The container of an boundary-point of a range is being set to either a node of an invalid type or a node with an ancestor of an invalid type." code: "2" nsresult: "0x805c0002 (NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE_ERR)" location: "chrome://google-toolbar-lib/content/toolbar.js Line: 2239"]
Chyba: uncaught exception: [Exception... "The container of an boundary-point of a range is being set to either a node of an invalid type or a node with an ancestor of an invalid type." code: "2" nsresult: "0x805c0002 (NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE_ERR)" location: "chrome://google-toolbar-lib/content/toolbar.js Line: 2239"]
Comment 1•15 years ago
|
||
This is not an exploitable security bug, it looks like a scripting bug in the Google Toolbar. What version of the Google Toolbar do you have?
If this only recently started spewing these errors it could be because of a Google Toolbar update, or because of a Firefox regression. Did this ever work for you? If it did, when did it break?
Group: core-security
Reporter | ||
Comment 2•15 years ago
|
||
Error:
Chyba: uncaught exception: [Exception... "Component returned failure code: 0x804b0012 (NS_ERROR_UNKNOWN_PROTOCOL) [nsIWebNavigation.loadURI]" nsresult: "0x804b0012 (NS_ERROR_UNKNOWN_PROTOCOL)" location: "JS frame :: chrome://global/content/viewSource.js :: viewSource :: line 221" data: no]
and
Chyba: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebProgress.removeProgressListener]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: removeProgressListener :: line 390" data: no]
Version Google Toolbar: 7.0.20091216Wb1
Comment 3•15 years ago
|
||
The errors in comment 2 are something else. The first one from viewSource.js is not any kind of a problem, it just means someone tried to view-source an unknown protocol. The way JavaScript components signal errors is by throwing exceptions so the presence of exceptions only tells you errors were encountered. They could be normal, expected, and handled errors (someone typing "view-source:foo://garbage" for instance) or they could indicate bugs in the component.
It doesn't do any good to lump different errors together in the same bug, this bug should stick to the boundary-point error in Google Toolbar
Comment 4•7 years ago
|
||
With WebExtensions being the only valid way of doing extensions in Firefox 57, I don't think this bug is still relevant.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•