Closed
Bug 1636089
Opened 4 years ago
Closed 4 years ago
Expose a good place to register JSProcessActor pairs
Categories
(Core :: DOM: Content Processes, enhancement)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla78
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: Yoric, Assigned: Yoric)
References
Details
Attachments
(1 file, 1 obsolete file)
JSWindowActor pairs are typically registered in BrowserGlue and ActorManagerParent.
We probably want something similar for JSProcessActor.
|
||
Comment 1•4 years ago
|
||
Yoric, is registering JSProcessActor pairs in the same place as JSWindowActor pairs not OK?
Nika says, IIUC, that registering JSWindowActor pairs in BrowserGlue and ActorManagerParent was a somewhat arbitrary design decision.
Flags: needinfo?(dteller)
|
Assignee | |
Comment 2•4 years ago
|
||
It's most likely ok. We just need to make it happen :)
Flags: needinfo?(dteller)
|
|
Assignee | |
Comment 3•4 years ago
|
||
|
||
Updated•4 years ago
|
Assignee: nobody → dteller
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 4•4 years ago
|
||
|
|
||
Updated•4 years ago
|
Attachment #9147388 -
Attachment is obsolete: true
Pushed by dteller@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/41012e39a75d ActorManagerParent.addJSProcessActors;r=kmag,geckoview-reviewers,snorp
|
||
Comment 6•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•