Breaks forum.fairphone.com

[Watilin]

This addon breaks https://forum.fairphone.com/ and any page of the same subdomain, whitelisted or not. This issue can potentially break other websites as well.

Steps to reproduce:

• Blacklisted (default):
  • Go to https://forum.fairphone.com/
  • Notice that the page is blank
  • Note the error message in the console: Uncaught Error: Permission denied to access property "catch"
• Whitelisted:
  • Open RejectServiceWorker menu and click "Add to Whitelist"
  • Refresh the page
  • Notice that the page is still blank
  • Notice the same error message in the console

The error message points to that section of the site's code:

navigator.serviceWorker.register((0, _getUrl.default)("/".concat(serviceWorkerURL))).catch(function (error) {
  ...

Apparently, the promise returned by .register() doesn't get the right permissions set, and the site attempting to access its .catch() method raises a permission error. Any website attempting to use .catch() (or any property that could get added to promises in the future) is subject to this issue as well.

[k08045kk]

Thank you for pointing this out.

I have confirmed the problem phenomenon. The problem was observed when the target page was viewed using the Firefox version. The problem was not observed when the target page was viewed using the Chrome version.

I'm still in the process of investigating, but it could be a profound problem with Firefox. It may take some time to fix. (There is also the issue of the AMO authentication process delay.)

workaround

• Use the Chrome version
• Use the RejectServiceWorker.user.js version
  • The same problem does occur in the case of blacklist.
  • The same problem does not occur in the case of whitelist. (because it does not work).
  • https://www.bugbugnow.net/2020/03/Reject-to-register-a-ServiceWorker.html

[k08045kk]

The problem has been fixed.

The root cause of the problem was that register() was returning the Promise of the content script. The site script (page script) was accessing the catch() of the content script's Promise, causing problems due to lack of permissions.

It has been fixed so that the return value of register() returns the Promise of the page script. The scope of the problem is limited to Firefox; Chrome is not affected.

I will be working on registering with AMO. However, due to a delay problem on the AMO side of the authentication process, it is not clear when the corresponding version (v0.5.0) will be available for Firefox.

That's all. Thank you very much.