Closed
Bug 1562005
Opened 5 years ago
Closed 5 years ago
Add in-tree documentation for JS Window Actors and how to port to them
Categories
(Core :: DOM: Core & HTML, task, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla70
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: mconley, Assigned: jdai)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
We should probably put this in as a sibling to https://firefox-source-docs.mozilla.org/dom/dom/Fission.html
Things to cover are probably:
- Mental model for JS Window Actors
- Things that are exposed on a JS Window Actor (although perhaps we can just link directly to the WebIDL definitions)
- How to port from message manager and framescripts to JS Window Actors
Updated•5 years ago
|
Flags: needinfo?(jdai)
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → jdai
Status: NEW → ASSIGNED
Type: defect → enhancement
Flags: needinfo?(jdai)
Priority: -- → P2
Updated•5 years ago
|
Type: enhancement → task
Assignee | ||
Comment 1•5 years ago
|
||
Pushed by jdai@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4321ec627e5d
Add in-tree documentation for JS Window Actors; r=nika
Comment 3•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Assignee | ||
Comment 4•5 years ago
|
||
Per discussion with mconley, I separated 3. How to port from message manager and framescripts to JS Window Actors
into Bug 1564359. As a consumer of JS Window Actors, front-end might have better equipped for clarity and what problems people individually try to solve.
You need to log in
before you can comment on or make changes to this bug.
Description
•