The spec currently defines FetchEvent.clientId as non-nullable. We still have the old nullable version. I had planned to wait to implement this in bug 1264177, but some WPT tests have changed to expect this. Some discussion here: https://github.com/w3c/ServiceWorker/issues/1266 Also, chrome has implemented and is planning to ship in chrome 66: https://www.chromestatus.com/feature/5942197618737152
Assignee: nobody → pjiang
Status: NEW → ASSIGNED
Make FetchEvent.clientId non-nullable
Comment on attachment 8997940 [details] Make FetchEvent.clientId non-nullable Blake Kaplan (:mrbkap) has approved the revision. https://phabricator.services.mozilla.com/D2789
Attachment #8997940 - Flags: review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/73847b793895 Make FetchEvent.clientId non-nullable r=mrbkap
You need to log in before you can comment on or make changes to this bug.