Closed Bug 1638756 Opened 5 years ago Closed 5 years ago

Do not force PROCESS target listening when listening to SERVICEWORKER

Categories

(DevTools :: Debugger, task, P3)

task

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1621337

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: nobody → jdescottes
Status: NEW → ASSIGNED
Whiteboard: dt-fission-m2-reserve → dt-fission-m2-mvp

Tracking dt-fission-m2-mvp bugs for Fission Nightly milestone (M6c)

Fission Milestone: --- → M6c
Attachment #9149790 - Attachment is obsolete: true
Attachment #9149791 - Attachment is obsolete: true
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Whiteboard: dt-fission-m2-mvp

Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.

Fission Milestone: M6c → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: