Closed
Bug 1656636
Opened 5 years ago
Closed 5 years ago
Test which JS modules and components are loaded during subframe content process startup
Categories
(Core :: DOM: Content Processes, enhancement, P2)
Core
DOM: Content Processes
Tracking
()
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
Attachments
(2 files)
With Fission, not all content processes contain toplevel content documents, and may only contain remote subframes. We should have a test for which JS modules and components are being loaded when loading a remote subframe, in addition to our existing tests for a toplevel document.
Assignee | ||
Comment 1•5 years ago
|
||
This should help us catch loads of JSActors which may be necessary for toplevel
document loads, but which need not be loaded within a remote subframe.
Assignee | ||
Comment 2•5 years ago
|
||
This avoids missing scripts which are filtered to not load on about:blank
documents.
Comment 3•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Component: General → DOM: Content Processes
Product: Firefox → Core
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/09512e1fb0d0
Part 1: Add a test for scripts loaded during subframe process startup, r=mconley,smacleod
https://hg.mozilla.org/integration/autoland/rev/3d41e1b571d0
Part 2: Load a real http URI in browser_startup_content, r=mconley,smacleod
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/09512e1fb0d0
https://hg.mozilla.org/mozilla-central/rev/3d41e1b571d0
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox81:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•