You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting privacy.antitracking.enableWebcompat to false will disable all ETP and State Partitioning web-compatibility features. Disabling these features can be useful when testing, to ensure your website is fully compatible with the State Partitioning mechanism in Firefox and it does not rely on temporary heuristics.
Features disabled by the pref include:
Storage access heuristics: Unpartitioned storage access can only be acquired via the Storage Access API.
Automatic storage access grants: document.requestStorageAccess will always prompt the user.
SmartBlock’s "unblock on opt-in" feature, which will allow certain trackers when users interact with them.
Any temporary anti-tracking exceptions granted to websites via the skip-listing mechanism.
Disable Heuristics
The following prefs can be used to disable individual storage access heuristics via the config editor:
WHAT does this achieve? SmartBlock heuristics are already behind a user gesture (clicking a login button no less). If you use a SSO to login, what do you gain besides possible breakage?
This would just becomes more stuff for me to maintain, test, answer questions about etc. No thank you. Make a real use case, or close, thanks
https://developer.mozilla.org/en-US/docs/Web/Privacy/State_Partitioning
Do we want to add
privacy.restrict3rdpartystorage.heuristic.*
to2702
?user.js/user.js
Lines 767 to 771 in 89bee0e
This would allow to disable opener heuristic (for example) while keeping other useful SmartBlock features.
The text was updated successfully, but these errors were encountered: