nsIRemoteAgent should return NS exceptions
Categories
(Remote Protocol :: Agent, defect, P1)
Tracking
(firefox73 fixed)
Tracking | Status | |
---|---|---|
firefox73 | --- | fixed |
People
(Reporter: ato, Assigned: ato)
References
Details
(Whiteboard: [puppeteer-alpha-reserve])
Attachments
(2 files)
The new nsIRemoteAgent
interface introduced with bug 1543115 did
not change the exceptions thrown internally by the class. To ensure
better interaction with consumers over XPIDL we should ensure the
JS implementation throws NS exceptions.
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
We first need to fix it so that XPCOM exceptions can be picked up by XPIDL consumers.
Assignee | ||
Comment 2•6 years ago
|
||
The nsIRemoteAgent interface introduced with bug 1543115 did
not change the exceptions thrown internally by the class. To ensure
better interaction with consumers over XPIDL we should ensure the
JS implementation throws NS exceptions.
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Now that nsIRemoteAgent propagates errors correctly to Rust we can
report errors back to the user when something terrible happens.
The effect of all this is that the startup handler can stop Firefox
when the remote agent fails to listen.
Assignee | ||
Updated•6 years ago
|
Comment 5•6 years ago
|
||
bugherder |
Description
•