Do not force PROCESS target listening when listening to SERVICEWORKER
Categories
(DevTools :: Debugger, task, P3)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
Attachments
(2 obsolete files)
In the initial implementation for ServiceWorkers in the target list for the content toolbox, we create a separate target list in the debugger to start fetching service worker targets.
This is necessary because the service worker TargetList will notify about serviceworker targets, but also about all process targets. When you have a content toolbox, it doesn't make sense to provide process targets from all processes to all the callbacks attached to the target list.
Ideally, we should be able to listen to service worker targets without polluting the targetlist with unexpected process targets. Process targets are necessary in order to retrieve service worker targets, but they should remain internal in this case.
I think we could directly use the LegacyProcessWatcher from the LegacyServiceWorkerWatcher.
| Assignee | ||
Comment 1•5 years ago
|
||
Depends on D74702
| Assignee | ||
Comment 2•5 years ago
|
||
Depends on D75752
Updated•5 years ago
|
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Tracking dt-fission-m2-mvp bugs for Fission Nightly milestone (M6c)
Updated•5 years ago
|
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.
Description
•