Closed
Bug 818224
Opened 12 years ago
Closed 12 years ago
Components.utils.reportError from chrome code running in a private window causes error messages to vanish
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
FIXED
mozilla21
Tracking | Status | |
---|---|---|
firefox20 | --- | fixed |
People
(Reporter: jdm, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
(deleted),
patch
|
bholley
:
review+
akeybl
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
Bug 769298 made errors originating from private windows not show up in the error console. Unfortunately, errors originating from chrome code don't go to the window console, so we need to avoid filtering these out or they are never seen.
Updated•12 years ago
|
OS: Mac OS X → All
Assignee | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
(In reply to Josh Matthews [:jdm] from comment #0)
> Unfortunately, errors originating from chrome code don't go
> to the window console, so we need to avoid filtering these out or they are
> never seen.
I don't understand this part. Can you explain?
Reporter | ||
Comment 3•12 years ago
|
||
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/console/content/consoleBindings.xml#172 makes any script errors from private windows not appear in the global error console. They also don't appear in the per-tab web console AFAIK, which means that they are completely invisible.
Reporter | ||
Comment 4•12 years ago
|
||
Sorry, comment 3 didn't specify tat I was talking about script errors from the chrome context of private windows.
Reporter | ||
Comment 5•12 years ago
|
||
This is noticeable by adding Cu.reportStringError('foo') to some chrome code that will be triggered from both public and private windows, and notice that the messages from private windows never show up.
Assignee | ||
Comment 6•12 years ago
|
||
(In reply to comment #5)
> This is noticeable by adding Cu.reportStringError('foo') to some chrome code
> that will be triggered from both public and private windows, and notice that
> the messages from private windows never show up.
Yeah. Or by actually causing a script error. To test this, I added |a.b();| to the end of browser/base/content/browser.js.
My patch simply makes sure that chrome script errors are never marked as coming from a private window.
Updated•12 years ago
|
Attachment #701380 -
Flags: review?(bobbyholley+bmo) → review+
Assignee | ||
Comment 7•12 years ago
|
||
Assignee | ||
Comment 8•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Assignee | ||
Comment 9•12 years ago
|
||
Comment on attachment 701380 [details] [diff] [review]
Patch (v1)
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 769298
User impact if declined: It would be nice to take this on Aurora since it makes debugging chrome js a bit easier, but it's not really a huge deal...
Testing completed (on m-c, etc.): Locally
Risk to taking this patch (and alternatives if risky): Not risky at all.
String or UUID changes made by this patch: None.
Attachment #701380 -
Flags: approval-mozilla-aurora?
Comment 10•12 years ago
|
||
Comment on attachment 701380 [details] [diff] [review]
Patch (v1)
If it makes debugging easier, it's early enough in the cycle to take. Approving for Aurora.
Attachment #701380 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee | ||
Comment 11•12 years ago
|
||
status-firefox20:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•