Open
Bug 1258066
Opened 9 years ago
Updated 2 years ago
navigator.registerProtocolHandler can cause uncaught newURI exception in WebContentConverter.js
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox48 | --- | affected |
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: testcase, Whiteboard: btpp-backlog)
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
JavaScript error: resource://app/components/WebContentConverter.js, line 138: uncaught exception: 2152398858
line 138:
> return Services.io.newURI(aURL, aOriginCharset, aBaseURI);
|
||
Comment 1•9 years ago
|
||
Blake, do we need to fix this sooner than "backlog" would imply?
Flags: needinfo?(mrbkap)
Whiteboard: btpp-backlog
|
||
Comment 2•9 years ago
|
||
Nope, this is purely cosmetic. We're properly catching and rethrowing all of the exceptions here but the error console gets a bit cluttered. If someone wanted to, they could figure out how to tell XPConnect to not report the exceptions until we get back to content, but that's pretty low priority.
Flags: needinfo?(mrbkap)
|
||
Updated•6 years ago
|
Priority: -- → P3
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•