[remote-dbg-next] Remove usage of client.request() for service workers

RESOLVED FIXED in Firefox 66

Status

enhancement
P1
normal
RESOLVED FIXED
8 months ago
6 months ago

People

(Reporter: jdescottes, Assigned: jdescottes)

Tracking

(Blocks 3 bugs)

unspecified
Firefox 66
Dependency tree / graph

Firefox Tracking Flags

(firefox66 fixed)

Details

Attachments

(7 attachments)

We should cleanup all the call sites in about:debugging that still rely on client.request: 

https://searchfox.org/mozilla-central/search?q=clientWrapper.request&case=false&regexp=false&path=

Instead to be consistent, we should get a front for the service worker and call methods on it.
Priority: -- → P3
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Priority: P3 → P1
Blocks: 1518122
Blocks: 1518123
Depends on D15378. This is an additional cleanup I forgot to include in the earlier patches.
We no longer use the request API in about:debugging so we can remove it from our wrapper.
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8ca78d645eed
Extract ServiceWorkerRegistrationList from worker-list.js;r=ochameau,ladybenko
https://hg.mozilla.org/integration/autoland/rev/2ecae1ee43a0
Move worker/worker-list.js to targets/worker-list;r=ochameau,ladybenko
https://hg.mozilla.org/integration/autoland/rev/a2289d2698b7
Create fronts for ServiceWorkerRegistration, PushSubscription and ServiceWorker;r=ochameau,ladybenko
https://hg.mozilla.org/integration/autoland/rev/247e6818b262
Return ServiceWorker fronts for installing, active and waiting workers;r=ochameau,ladybenko
https://hg.mozilla.org/integration/autoland/rev/08b043c4ef1b
Extract service worker actors to dedicated files;r=ochameau,ladybenko
https://hg.mozilla.org/integration/autoland/rev/ab1bfb032425
Remove request API from client wrapper;r=ladybenko
Depends on D16022 . Minor fix, just reordering a spec definition.
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/639924062722
Reorder specs to be alphabetically sorted;
You need to log in before you can comment on or make changes to this bug.