Service Worker list should also include iframe origins
Categories
(DevTools :: Application Panel, enhancement, P4)
Tracking
(Fission Milestone:Future)
| Fission Milestone | Future |
People
(Reporter: Harald, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-future)
User Story
As a developer of a complex web application that includes some microservices via iframes I need to inspect service workers across all frames. Requirement: The default origin list that filters down the SW list in the application panel should include the top-level origin and all iframes.
Updated•8 years ago
|
| Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 2•6 years ago
|
||
From Bug 1667755
STRs:
- open http://janodvarko.cz/tests/fission/case7/index.html
- open the Application panel
ER: We should see the service worker registered by the frame pointing to https://firefox-devtools-waiting-sw.glitch.me/ . Note that if you open https://firefox-devtools-waiting-sw.glitch.me/ in a new tab and open the application panel for this tab, you will successfully see the service worker registered.
Currently the application panel is filtering the list of service workers based on the domain of the top target:
// Filter out workers from other domains
const domainWorkers = registrations.filter(
x => x.workers.length > 0 && new URL(x.workers[0].url).hostname === domain
);
The domain here comes from the component props, which originally comes from:
updateDomain() {
this.actions.updateDomain(this.toolbox.target.url);
},
Comment 3•5 years ago
|
||
STR:
- Load http://janodvarko.cz/tests/fission/case7/index.html
- Wait till the remote iframe is fully loaded (it goes from Glitch and might take some time)
- Open DevTools Toolbox and select the Appliction panel.
- The panel should show one Service workers (sw.js) from firefox-devtools-waiting-sw.glitch.me
You can also click the link in Open the remote iframe in another tab to see that the SW is visible in the App panel if loaded in top level document.
Honza
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Tracking dt-fission-m3-reserve bugs for Fission M8 (blocking Release channel experiment, but not Beta experiment).
Comment 5•5 years ago
|
||
Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.
Updated•4 years ago
|
Description
•