Register main process target on server start

RESOLVED FIXED

Status

enhancement
P1
normal
RESOLVED FIXED
5 months ago
4 months ago

People

(Reporter: ochameau, Assigned: ochameau)

Tracking

(Blocks 1 bug)

Details

Attachments

(3 attachments)

For now, we instanciate the MainProcessTarget on-demand. We typically do that when the /json/version endpoint is queried.
But chromium do expose this target by default. Actually when you execute:

$ chromium-browser --remote-debugging-port=9000

It prints this particular target's websocket URL:

DevTools listening on ws://127.0.0.1:9000/devtools/browser/4f49392c-d41e-456a-9756-1ae56be75806

It means that the /devtools/browser/${UUID} endpoint should be registered on server startup. And regarding how our implementation works, it means that the MainProcessTarget class should be instanciated on server startup.

Status: NEW → ASSIGNED
Priority: -- → P1
Attachment #9054800 - Attachment description: Bug 1539221 - Fix missing `formatError` export. → Bug 1539221 - Fix piping of errors back to the client due to missing formatError symbol.
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2f0524895cf3
Fix piping of errors back to the client due to missing formatError symbol. r=ato
https://hg.mozilla.org/integration/autoland/rev/d16ffacbce08
Fix DOMContentLoadedPromise when the document is in a state between DOMContentLoaded and load event. r=ato
https://hg.mozilla.org/integration/autoland/rev/8cfc47737c53
Register main process target on server start. r=ato
You need to log in before you can comment on or make changes to this bug.