You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because having a sw.js sitting in the root is just ugly.
However, the Service-Worker-Allowed header is mega confusing to use, and the corresponding spec text is (for me?) very hard to understand.
Can we please add an example for how to use this in the common case above... also, can we please add some examples for how the {scope: "whatever"} and the Service-Worker-Allowed header value are combined to come up with maxScope, etc.?
Thanks! ❤️
The text was updated successfully, but these errors were encountered:
(FWIW, Chrome's error messages when using Service-Worker-Allowed are super helpful... I was trying to do this in Firefox and it currently provides little help apart from the security error 😿).
I imagine a lot of people will want to do this:
Because having a sw.js sitting in the root is just ugly.
However, the
Service-Worker-Allowed
header is mega confusing to use, and the corresponding spec text is (for me?) very hard to understand.Can we please add an example for how to use this in the common case above... also, can we please add some examples for how the
{scope: "whatever"}
and theService-Worker-Allowed
header value are combined to come up withmaxScope
, etc.?Thanks! ❤️
The text was updated successfully, but these errors were encountered: