Closed
Bug 1265775
Opened 9 years ago
Closed 9 years ago
replace uses of Cu.reportError
Categories
(DevTools :: Framework, enhancement, P1)
DevTools
Framework
Tracking
(firefox49 fixed)
Tracking | Status | |
---|---|---|
firefox49 | --- | fixed |
People
(Reporter: tromey, Assigned: jlong)
References
Details
(Whiteboard: [devtools-html])
Attachments
(2 files, 2 obsolete files)
53.09 KB,
patch
|
tromey
:
review+
|
Details | Diff | Splinter Review |
9.05 KB,
patch
|
tromey
:
review+
|
Details | Diff | Splinter Review |
Replace Cu.reportError uses in devtools for de-chrome-ification project.
Updated•9 years ago
|
Severity: normal → enhancement
Whiteboard: [devtools-html]
Reporter | ||
Comment 1•9 years ago
|
||
Note also bug 1179970 (wontfix, but for the other direction); and bug 877389 (for the rest
of the browser).
Reporter | ||
Comment 2•9 years ago
|
||
Maybe .catch(Cu.reportError) can use .catch(console.error), though many places
in the tree use .catch(e => console.error(e)), leading us to wonder about "this" binding.
Reporter | ||
Comment 3•9 years ago
|
||
:ochameau points out:
<ochameau> tromey: hey! about you comment on console.log. try
console.log.apply(null, ["plop"]) in a webpage, it will throw
<ochameau> tromey: the console in modules may be bound, but not the one in
documents
<ochameau> tromey: so it is better to assume it is not bound, as we may use
console api from tools document scope
Given this I think there are some existing latent bugs where something like
.then(null, console.error) is used.
Reporter | ||
Comment 4•9 years ago
|
||
One option here is to use ThreadSafeDevToolsUtils.reportException
Updated•9 years ago
|
Assignee: nobody → jlong
Status: NEW → ASSIGNED
Iteration: --- → 49.1 - May 9
Flags: qe-verify-
Priority: -- → P1
Assignee | ||
Comment 5•9 years ago
|
||
Initial pass
Assignee | ||
Comment 6•9 years ago
|
||
Rebased on top of fx-team
Attachment #8748265 -
Attachment is obsolete: true
Assignee | ||
Comment 7•9 years ago
|
||
Let's see what this does: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f5be54cf49ca
Assignee | ||
Comment 8•9 years ago
|
||
Assignee | ||
Comment 9•9 years ago
|
||
Attachment #8748270 -
Attachment is obsolete: true
Attachment #8749244 -
Flags: review?(ttromey)
Reporter | ||
Comment 10•9 years ago
|
||
Comment on attachment 8749244 [details] [diff] [review]
1265775.patch
Review of attachment 8749244 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good. Thank you for doing this.
Attachment #8749244 -
Flags: review?(ttromey) → review+
Assignee | ||
Comment 12•9 years ago
|
||
I still need to replace any instances in the devtools/shared directory.
Keywords: leave-open
Comment 13•9 years ago
|
||
bugherder |
Assignee | ||
Comment 14•9 years ago
|
||
Fairly small patch. I ignored a few places that clearly won't be loaded in the client, like Loaders.jsm
Attachment #8750449 -
Flags: review?(ttromey)
Assignee | ||
Comment 15•9 years ago
|
||
Reporter | ||
Comment 16•9 years ago
|
||
Comment on attachment 8750449 [details] [diff] [review]
1265775-shared.patch
Review of attachment 8750449 [details] [diff] [review]:
-----------------------------------------------------------------
Thank you.
This patch looks good to me.
I am perhaps mildly worried about testing it. For the most part I think it's not worth worrying about; but for example the previous transport.js code made me wonder if something unusual is going on there.
Attachment #8750449 -
Flags: review?(ttromey) → review+
Assignee | ||
Updated•9 years ago
|
Keywords: leave-open
Assignee | ||
Comment 17•9 years ago
|
||
Will push this once the tree opens
Updated•9 years ago
|
Iteration: 49.1 - May 9 → 49.2 - May 23
Comment 19•9 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox49:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 49
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•