remove confusing comment

> serviceWorkers require an "Allow" permission

I made this change as part of v103 (after we finally migrated off lifetime cookie policy), but I cannot for the life of me work out why I mentioned SWers needing an allow permission - there is no such thing in ctrl-I or under privacy> permissions. (I checked ESR102, and current)

If anyone can enlighten me, speak up
This commit is contained in:
Thorin-Oakenpants 2024-06-07 03:29:25 +00:00 committed by GitHub
parent 434fa6bb77
commit 60db0ebac4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -665,9 +665,8 @@ user_pref("privacy.clearOnShutdown_v2.historyFormDataAndDownloads", true); // [F
/** SANITIZE ON SHUTDOWN: RESPECTS "ALLOW" SITE EXCEPTIONS FF103+ | v2 migration is FF128+ ***/
/* 2815: set "Cookies" and "Site Data" to clear on shutdown (if 2810 is true) [SETUP-CHROME]
* [NOTE] Exceptions: A "cookie" block permission also controls "offlineApps" (see note below).
* serviceWorkers require an "Allow" permission. For cross-domain logins, add exceptions for
* both sites e.g. https://www.youtube.com (site) + https://accounts.google.com (single sign on)
* [NOTE] Exceptions: A "cookie" block permission also controls "offlineApps" (see note below). For cross-domain logins,
* add exceptions for both sites e.g. https://www.youtube.com (site) + https://accounts.google.com (single sign on)
* [NOTE] "offlineApps": Offline Website Data: localStorage, service worker cache, QuotaManager (IndexedDB, asm-cache)
* [NOTE] "sessions": Active Logins (has no site exceptions): refers to HTTP Basic Authentication [1], not logins via cookies
* [WARNING] Be selective with what sites you "Allow", as they also disable partitioning (1767271)