Closed Bug 1543904 Opened 1 year ago Closed 1 year ago

[remote-dbg-next] Service Worker debugging should be disabled if sw-e10s-refactor is enabled

Categories

(DevTools :: about:debugging, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jdescottes, Unassigned)

References

(Blocks 1 open bug)

Details

We previously enabled service-worker-debugging when the sw-e10s-refactor was enabled. However the latest changes from Bug 1231213 will break service worker debugging.

From Perry:
"[...] there is no way to get the nsIWorkerDebugger. Previously it was obtained in the parent process from a WorkerPrivate object, but now all of the WorkerPrivate objects have been moved into the child process [...] I guess Service Workers debugging is completely broken until we coordinate how to implement getting and using the nsIWorkerDebuggers"

Based on this we should review the state of service worker debugging as soon as Bug 1231213 lands and update our UI accordingly.

We can simply update https://searchfox.org/mozilla-central/source/devtools/shared/multi-e10s-helper.js in order to disable start/debug features from the new about:debugging, but we should check if other features also need to be disabled. (or if the UI is significantly broken etc...)

Priority: -- → P2
Whiteboard: high-priority-reserved
Priority: P2 → P3
Whiteboard: high-priority-reserved → high-priority-reserve

It doesn't look like Bug 1231213 will land in 68, so removing the priority flag.

Whiteboard: high-priority-reserve

We should have working devtools when the refactor lands, this is now invalid.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.