Closed
Bug 1648109
Opened 5 years ago
Closed 5 years ago
Report pretty error messages from JSContentActor APIs
Categories
(Core :: DOM: Content Processes, enhancement, P3)
Core
DOM: Content Processes
Tracking
()
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
Attachments
(1 file)
Unlike JSWindowActor, the manager for JSContentActor is nsIDOMProcess{Parent,Child}
, which is an xpcom interface, rather than a webidl one. The errors returned from this function are simple NS_ERROR_*
errors, and don't have as nice custom error messages as WindowGlobal{Parent,Child}
can.
It is possible to have a WebIDL-style ErrorResult&
taking method defined on the implementations of these types, and call it from the nsIDOMProcess
interface, which could allow for nicer error reporting.
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → nika
Status: NEW → ASSIGNED
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f6373dd0caa0
Report GetActor exceptions directly to the JSContext, r=kmag
Comment 3•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
Comment 4•5 years ago
|
||
bugherder |
You need to log in
before you can comment on or make changes to this bug.
Description
•