Closed
Bug 815973
Opened 12 years ago
Closed 8 years ago
SocialErrorListener also catches errors from XHR
Categories
(Firefox Graveyard :: SocialAPI, defect)
Firefox Graveyard
SocialAPI
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Felipe, Unassigned)
Details
Mark astutely pointed out that the SocialErrorListeners (http://mxr.mozilla.org/mozilla-central/source/browser/base/content/browser-social.js#1040) that are attached to the content panels also captures errors from XHR done by those pages, a case where the page itself is usually responsible for handling the error conditions. Should these listeners ignore those errors? what about non-toplevel load errors (like iframes inside the page loading a 404)? (On the other hand this overeager listener helped find bug 815053)
Comment 1•8 years ago
|
||
Felipe, is this bug still valid, or is it obsolete after the recent overhaul of the Social API?
Flags: needinfo?(felipc)
Reporter | ||
Comment 2•8 years ago
|
||
Let me redirect this to Shane since I don't know if this code still exist or if it was removed in the recent overhaul
Flags: needinfo?(felipc) → needinfo?(mixedpuppy)
Comment 3•8 years ago
|
||
The error listener still exists in social-content.js, it is only used in the share panel now. I'm not certain it is as over eager as it used to be.
Flags: needinfo?(mixedpuppy)
Comment 4•8 years ago
|
||
Actually, haven't seen a problem from this in ages, closing it.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•