Closed
Bug 1258071
Opened 9 years ago
Closed 6 years ago
FeedConverter throws raw nsresults instead of exceptions (error from ContentLinkHandler.jsm on a document with <link rel="foo" href="feed:javascript:1"> fetching link.href property), should be using Components.Exception
Categories
(Firefox Graveyard :: RSS Discovery and Preview, defect, P3)
Firefox Graveyard
RSS Discovery and Preview
Tracking
(firefox48 affected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox48 | --- | affected |
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(1 file)
102 bytes,
text/html
|
Details |
JavaScript error: resource://app/modules/ContentLinkHandler.jsm, line 41: uncaught exception: 2152398858
Comment 1•9 years ago
|
||
It'd probably be worth having eslinting for this pattern. Mossop, is this something that you can throw on the eslint pile of work that you seem to be doing? :-)
Component: General → RSS Discovery and Preview
Flags: needinfo?(dtownsend)
Summary: ContentLinkHandler.jsm error with <link rel="foo" href="feed:javascript:1"> → FeedConverter throws raw nsresults instead of exceptions (error from ContentLinkHandler.jsm on a document with <link rel="foo" href="feed:javascript:1"> fetching link.href property), should be using Components.Exception
Comment 2•9 years ago
|
||
So to be clear, the real issue here are things like:
https://dxr.mozilla.org/mozilla-central/rev/55d557f4d73ee58664bdf2fa85aaab555224722e/browser/components/feeds/FeedConverter.js#509
Comment 3•9 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #1)
> It'd probably be worth having eslinting for this pattern. Mossop, is this
> something that you can throw on the eslint pile of work that you seem to be
> doing? :-)
Sorry, I haven't even had time to finish up bug 1257246, I don't have any time available for this right now.
Flags: needinfo?(dtownsend)
Comment 4•9 years ago
|
||
The patches from bug 1260511 will help a bit here in the sense that the raw number will get converted to an exception object. But 2152398858 = 0x804b000a looks to me like NS_ERROR_MODULE_NETWORK, and in particular NS_ERROR_MALFORMED_URI (yeah, I know, linked from comment 2), which is not an exception that should ever happen on the web. I think typically SYNTAX_ERR is used for cases like this.
Updated•8 years ago
|
Blocks: CVE-2017-5382
Updated•7 years ago
|
Priority: -- → P3
Comment 5•6 years ago
|
||
The feed preview code has been removed by bug 1477669.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•