Closed
Bug 779680
Opened 12 years ago
Closed 12 years ago
about:neterror's GoOnline() should be invoked from events, not nsDOMWindowUtils
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
FIXED
mozilla17
People
(Reporter: mccr8, Assigned: Unfocused)
References
Details
Attachments
(1 file)
4.26 KB,
patch
|
Dolske
:
review+
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
The current method is gross.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bmcbride
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•12 years ago
|
||
Made the event listeners in browser.js use capture to ensure they get the event first, before the handler in the page. And AFAICT it didn't even break anything!
(Tagging dolske for r? as punishment.)
Attachment #648605 -
Flags: review?(dolske)
Attachment #648605 -
Flags: review?(bzbarsky)
Comment 2•12 years ago
|
||
Comment on attachment 648605 [details] [diff] [review]
Patch v1
r=me
Attachment #648605 -
Flags: review?(bzbarsky) → review+
Comment 3•12 years ago
|
||
Comment on attachment 648605 [details] [diff] [review]
Patch v1
Why the capturing listener? So we trigger online-mode before the page starts the reload?
Probably worth a comment in retryThis that the browser.js code handles the go-online thing.
Attachment #648605 -
Flags: review?(dolske) → review+
Reporter | ||
Comment 4•12 years ago
|
||
Is nsDOMWindowUtils::GoOnline still called anywhere after this patch?
Assignee | ||
Comment 5•12 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #4)
> Is nsDOMWindowUtils::GoOnline still called anywhere after this patch?
Bah, yes, because we have multiple copies of netError.xhtml. Filed bug 781688 and bug 781689, which I'll handle today. AFAICT, there are no more uses of it once those are fixed (I even checked comm-central!).
Reporter | ||
Comment 6•12 years ago
|
||
Great, thanks!
Assignee | ||
Comment 7•12 years ago
|
||
(In reply to Justin Dolske [:Dolske] from comment #3)
> Why the capturing listener? So we trigger online-mode before the page starts
> the reload?
Yep.
> Probably worth a comment in retryThis that the browser.js code handles the
> go-online thing.
Will do.
Assignee | ||
Comment 8•12 years ago
|
||
Comment 9•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Comment 10•12 years ago
|
||
(In reply to Blair McBride from comment #5)
> (I even checked comm-central!)
All you did was notice that we don't override aboutNetError.xhtml, but sadly you failed to inform us that we now need to create an alternative way of going online in front-end code...
Assignee | ||
Comment 11•12 years ago
|
||
Sorry, yes, I meant to file a separate bug for that the other day, but forgot. Filed bug 782892.
Reporter | ||
Updated•12 years ago
|
No longer blocks: CVE-2012-3986
You need to log in
before you can comment on or make changes to this bug.
Description
•