clod81 / block_service_workers Goto Github PK

There are cases when on some domains service_worker.js is passed through the address of the article which leads to a kind of "bug"

It would be nice to be able to block the worker globally for the entire domain.

https://lit.dev/playground does not work when whitelisted:

playground-service-worker-proxy.html:11  Uncaught (in promise) TypeError: a.addEventListener is not a function
    at playground-service-worker-proxy.html:11:1093
17:14:38.727 playground-service-worker-proxy.html:11  Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'state')
    at playground-service-worker-proxy.html:11:782
    at s (playground-service-worker-proxy.html:11:943)
    at playground-service-worker-proxy.html:11:1087

Block Service Workers 1.0.0, Chromium 72.0.3626.121 (Official Build) (64-bit) on FreeBSD-CURRENT.

tl;dr at https://mobile.twitter.com/settings/push_notifications after I click NO to block, I get none of these things:

1. a block
2. the service worker at chrome://serviceworker-internals
3. push notification preferences at https://mobile.twitter.com/settings/push_notifications

If, instead, I click YES to allow then there's an apparent allowance but still, non-appearance of preferences:

I waited a long time for preferences to appear, they didn't.

Quit, relaunched Chromium: no difference (still non-appearance of preferences within the Twitter window).

A few seconds after I disabled the extension, preferences appeared:

– and I gained a worker for mobile Twitter.

Probably not an issue with Block Service Workers, but this puzzles me and you might have an explanation.

Outdated Block Service Workers 0.3.6 with Waterfox ~56.2.7.1 on (unsupported) FreeBSD-CURRENT. (Waterfox 56.0 was based on Firefox 56.0.2.)

With the extension added to a new profile, blockage seems to occur easily. If I remove then block then Shift-reload https://mail.google.com/mail/u/0/#inbox, blockage occurs around ten seconds after completion of the load 👍

With the extension added to an older profile, I can easily get a block on e.g. the worker for WhatsApp Web, however I can not get a block on Gmail – not even when this extension alone is enabled. I have tried a few tricks, including repeat reloads (without overriding the cache) but I haven't found a working trick.

A last resort should be a refresh of Waterfox, but I'd like to understand what might prevent the extension from working in this case.

Please, any ideas?

Re: 7a4bb84 I see that Firefox is no longer supported, so I'll understand if you want to simply close this issue without responding.

TIA

I see you haven’t entered a license file, maybe you should.
https://creativecommons.org is your friend :-)

Regards
Vincenzo

At the moment using confirm, which disappears on tab switch, marking the domain as non allowed to use SW without user deciding

Hi congratulations for the extension, I propose to restructure the extension starting from the generator: https://github.com/yeoman/generator-chrome-extension

Rather than per whole domain, as currently is

When user selects to disallow SW for a specific domain, deregister all existing ones (if any)

My Chromebooks were freezing up until I removed all my service workers. Now I have enough ram to stop the virtual memory thrashing, but I'd sure like to not have to say no to every website I visit, as most want to install a service worker theses days.

"Service workers in my browser are like barnacles on my Internet surfboard." Mark Zinzow

Per domain, or the whole lot

Hi,

When the extension is installed and enabled, the site https://vscode.dev is not working, with this error:

In the Javascript console:

(index):1 DOMException: Failed to execute 'postMessage' on 'Window': TrustedScriptURL object could not be cloned.
    at ServiceWorkerContainer.__bsw_override__ [as register] (<anonymous>:1:480)
    at https://vscode.dev/:1:6021
    at Generator.next (<anonymous>)
    at r (https://vscode.dev/:1:3008)

If I disable manually the extension, the site loads fine.

Is there some configuration to disable the extension only for this site, or some option to make the site work with the extension, or is it a bug in the extension itself?

Thanks for your help.

When registration is fired later on by a domain and it's not the focused tab, the allow/block notification is triggered for the wrong domain