Add remote-agent-requested system notification
Categories
(Remote Protocol :: Agent, enhancement, P1)
Tracking
(firefox72 fixed)
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: ato, Assigned: ato)
References
Details
(Whiteboard: [puppeteer-alpha])
Attachments
(1 file)
The remote agent currently waits for the sessionstore-windows-restored
event, but we should reverse the model so that application code can
decide when it is safe to start the remote agent.
This is similar to the model used for Marionette, which listens for
marionette-startup-requested
. We could probably rely on exactly
this event at the moment, but in the interest of decoupling Marionette
from the remote agent we should probably have a separate notification
for the remote agent.
Assignee | ||
Comment 1•5 years ago
|
||
The remote agent startup code changes as part of bug 1543115
which means it is a short-term blocker for addressing this.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
This moves the Chromium remote debugging protocol implementation
in Firefox from using sessionstore-windows-restored to a new
remote-startup-requested notification observer.
This change makes it possible for applications to explicitly decide
at which stage it is considered safe to initialise the remote agent
listener. It is safe to emit this notification at any time since
the observer for it is only registered after the --remote-debugger
flag is is used.
The remote debugger only supports Firefox, so this patch does not
take care of GeckoView/Android.
Pushed by ato@sny.no: https://hg.mozilla.org/integration/autoland/rev/e260a401d107 remote, browser: request remote agent startup; r=florian,remote-protocol-reviewers,maja_zf
Comment 4•5 years ago
|
||
bugherder |
Description
•