Serviceworkers are disabled in Mozilla Firefox (82.0.2)
Categories
(Core :: DOM: Service Workers, defect)
Tracking
()
People
(Reporter: balazs.kiss, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
Tried to open a site with serviceworker.
Actual results:
The site failed to load with the message that serviceworkers are disabled in Firefox.
Expected results:
if ('serviceWorker' in navigator) {
// Do a one-off check to see if a service worker's in control.
if (navigator.serviceWorker.controller) {
console.log(This page is currently controlled by: ${navigator.serviceWorker.controller}
);
} else {
console.log('This page is not currently controlled by a service worker.');
}
} else {
console.log('Service workers are not supported.');
}
Running this code returns that ServiceWorkers are disabled.
Opening about:debugging#/runtime/this-firefox indicates the same with the yellow alert.
However, my settings (about:config) dom.serviceWorkers.enabled is enabled. I am not using private browsing, and I am not using ESR. (Current version: (82.0.2))
The site works on IE, Edge, and the developer of the site said that on their firefox version as well.
appCodeName: "Mozilla"
appName: "Netscape"
appVersion: "5.0 (Windows)"
buildID: "20201027185343"
Comment 1•4 years ago
|
||
Andrew any idea what might be going on here?
Comment 2•4 years ago
|
||
I'm not sure what the yellow alert is for about:debugging#/runtime/this-firefox
. My best guess is it's from https://searchfox.org/mozilla-central/source/devtools/client/aboutdebugging/src/components/ServiceWorkersWarning.js which localizes to "Your browser configuration is not compatible with Service Workers. <a>Learn more</a>". If it's that, then this about:debugging logic is basing its decision on the determination here that is checking the dom.serviceWorkers.enabled
pref and the browser.privatebrowsing.autostart
pref. Note that both of these preferences only take effect at startup, so the browser needs to be restarted.
Reporter, can you re-confirm the status of those preferences and what specific error message you're seeing in about:debugging? If it seems like things are working, perhaps visit https://firefox-storage-test.glitch.me/ and verify that all four subsystems report "Good: Totally Working. (fullyOperational)"?
Comment 3•4 years ago
|
||
Thank you for your time and effort!
Yep, the alert is exactly that which you described.
Requested properties:
dom.serviceWorkers.enabled true
browser.privatebrowsing.autostart true
The said test page indicates that the "Cache.API" is (fullyBroken).
Images: https://drive.google.com/drive/folders/1dj3AXyjphY1HcJ6Hp5_PRgI7ajI_Vwh-?usp=sharing
Cheers,
Balázs
(from my private account)
Comment 4•4 years ago
|
||
ServiceWorkers and the Cache API don't work in private browsing mode at this time, duping this bug to the general tracking bug for that.
Description
•