搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Service Worker cannot register

  • 无回复
  • 1 人有此问题
  • 16 次查看
more options

I am using Firefox 96.0.1 on macOS Monterey 12.1

If you have "'Delete cookies and site data when Firefox is closed checked in Privacy & Security/Cookies and Site Data then this causes sites that use a service worker to fail registration with the error:

"Failed to register/update a ServiceWorker for scope https://every-layout.dev/: Storage access is restricted in this context due to user settings or private browsing mode."

This *only* occurs with Firefox, Safari, Chrome, Brave etc. all register the service worker OK. I know the workaround is to put in an Exception to Allow but this should not be necessary. In this case the service worker is use to provide access to paid for content and off-line reading.

I contacted the site's developers and they tell me that they have been waiting for ages for Mozilla to fix this issue and suggested I used an alternative browser.

Can anyone explain why Firefox behaves in this way and if this "feature" will be fixed on future releases?

Thanks

John

I am using Firefox 96.0.1 on macOS Monterey 12.1 If you have "'Delete cookies and site data when Firefox is closed''' checked in Privacy & Security/Cookies and Site Data then this causes sites that use a service worker to fail registration with the error: "Failed to register/update a ServiceWorker for scope https://every-layout.dev/: Storage access is restricted in this context due to user settings or private browsing mode." This *only* occurs with Firefox, Safari, Chrome, Brave etc. all register the service worker OK. I know the workaround is to put in an Exception to Allow but this should not be necessary. In this case the service worker is use to provide access to paid for content and off-line reading. I contacted the site's developers and they tell me that they have been waiting for ages for Mozilla to fix this issue and suggested I used an alternative browser. Can anyone explain why Firefox behaves in this way and if this "feature" will be fixed on future releases? Thanks John