Closed Bug 1590828 Opened 6 years ago Closed 6 years ago

nsIRemoteAgent should return NS exceptions

Categories

(Remote Protocol :: Agent, defect, P1)

defect

Tracking

(firefox73 fixed)

RESOLVED 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.

Depends on: 1543115
Priority: -- → P3
Whiteboard: [puppeteer-alpha]
Whiteboard: [puppeteer-alpha] → [puppeteer-alpha-reserve]
See Also: → 1600111
Depends on: 1600121

We first need to fix it so that XPCOM exceptions can be picked up by XPIDL consumers.

Depends on: 1600111
See Also: 1600111
Blocks: 1600139

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.

Assignee: nobody → ato

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.

Status: NEW → ASSIGNED
Priority: P3 → P1
Blocks: 1600330
Pushed by atolfsen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d7daba7f077e remote: return NS exceptions from nsIRemoteAgent r=remote-protocol-reviewers,whimboo,maja_zf https://hg.mozilla.org/integration/autoland/rev/eca7999b3814 remote: take appropriate action on errors during startup r=remote-protocol-reviewers,maja_zf,whimboo
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: