Non-registrations and losses of service workers

[grahamperrin]

NoScript 11.0.11 with Firefox 72.0: service workers are lost, I see no way to prevent the loss.

Please, is this a known issue?

Background (before I identified NoScript as a cause): Absence of service workers in Firefox 72 : firefox

[grahamperrin]

With a different profile, testing NoScript alone, I find prevention of registration but not loss of registered service workers.

Screen recording:

https://s.put.re/Nyu3Ek5J.mp4

If there's a way for NoScript to allow registration, this will be a step towards helping me to identify what may be partly an extensions conflict.

Thanks

[Giorgio Maone]

As far as I can see, this is not a general problem but specific to some service workers (like the example you linked).
For instance I've got no troubles with those at youtube, gmail and other popular services.
In this case there's actually a pretty hairy user interface bug, due to the fact that scripts imported by service workers with importScripts() are intercepted by webRequest with no specific tab associated, and therefore they are cannot reported in the UI.
The one which is blocked and prevents the routes.glitch.me/sw.js service from being registered is at storage.googleapis.com.
Just add it set to TRUSTED in the NoScript Options tab, and registration should succeed.
I'm looking for ways to work-around the "no tab id" issue in next NoScript release, so that scripts imported by service workers can be reported as well.

[grahamperrin]

storage.googleapis.com

Excellent. Thanks for the explanation!

Now I need to discover what causes losses – https://discourse.mozilla.org/t/-/51431 ... ahamperrin