Closed Bug 1239113 Opened 4 years ago Closed 10 months ago

about:serviceworkers should fire update in current process when possible

Categories

(Core :: DOM: Service Workers, defect, P3)

32 Branch
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: bkelly, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [e10s-multi:-], SW-CLEANUP)

+++ This bug was initially created as a clone of Bug #1238990 +++

Bug 1238990 made our normal service worker update triggers fire in the current local process.  This bug is to fix about:serviceworkers to do the same where possible.  When not possible (due to appId) it will fire in the first process it sees with the correct appId.
Summary: service worker should not propagate updates across processes → about:serviceworkers should fire update in current process when possible
As about:serviceworkers is being deprecated, we probably won't fix this.

However, if firing an update is an important feature that about:debugging should support, please either update this bug accordingly, or file a new bug.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
If about:debugging gets an update button it would have to do this as well.  Let's leave this open until about:serviceworkers actually goes away.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
I'm not currently working this, though.
Assignee: bkelly → nobody
Depends on: 1220747
Whiteboard: [e10s-multi:-]
Priority: -- → P3
Whiteboard: [e10s-multi:-] → [e10s-multi:-], SW-CLEANUP

We're planning to remove about:serviceworkers in the near term and the parent-intercept changes as already landed mean that this will not be a problem for about:debugging. (Specifically, there's no way to trigger the update in the wrong process.)

Status: REOPENED → RESOLVED
Closed: 4 years ago10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.