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
It looks like that in order to disable Privacy Badger on a site in MV3, "allowAllRequests" rules are not enough, and we should also make session "allow" rules for requests with the disabled site domain as the initiator. Otherwise, we will continue to block service worker requests associated with the disabled sites.
These "allow" rules should be scoped to to tab IDs with tabs.TAB_ID_NONE, to avoid allowing requests from the disabled site initiator when the disabled site initiator is in a frame.
These rules have to be session rules because tab ID scoping isn't supported in dynamic rules.
It looks like that in order to disable Privacy Badger on a site in MV3, "allowAllRequests" rules are not enough, and we should also make session "allow" rules for requests with the disabled site domain as the initiator. Otherwise, we will continue to block service worker requests associated with the disabled sites.
These "allow" rules should be scoped to to tab IDs with
tabs.TAB_ID_NONE
, to avoid allowing requests from the disabled site initiator when the disabled site initiator is in a frame.These rules have to be session rules because tab ID scoping isn't supported in dynamic rules.
w3c/webextensions#737 (comment)
https://github.com/uBlockOrigin/uBOL-home/blob/main/chromium/js/ruleset-manager.js#L519-L536
The text was updated successfully, but these errors were encountered: