The feature only provides meaningful protection if 3rd party cookies are already restricted. I recommend to enable the feature only for cookie behavior 1,3,4,5. That matches [the behavior of the existing redirect tracking protection](https://developer.mozilla.org/en-US/docs/Web/Privacy/Redirect_tracking_protection#debugging). See https://searchfox.org/mozilla-central/rev/8c3ca2f5a74e0ba59c3d9dddf5468a2ffab13467/netwerk/cookie/nsICookieService.idl#59-65 for a list of supported cookie behaviors. We need to take private browsing into account which can have a separate cookie behavior value than normal browsing.
Bug 1892494 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The feature only provides meaningful protection if 3rd party cookies are already restricted. I recommend to enable the feature only for cookie behavior 1,3,4,5. That matches [the behavior of the existing redirect tracking protection](https://developer.mozilla.org/en-US/docs/Web/Privacy/Redirect_tracking_protection#debugging). See https://searchfox.org/mozilla-central/rev/8c3ca2f5a74e0ba59c3d9dddf5468a2ffab13467/netwerk/cookie/nsICookieService.idl#59-65 for a list of supported cookie behaviors. We need to take private browsing into account which can have a separate cookie behavior value than normal browsing. Edit: This might be a good place to add the logic: https://searchfox.org/mozilla-central/rev/8c3ca2f5a74e0ba59c3d9dddf5468a2ffab13467/toolkit/components/antitracking/bouncetrackingprotection/BounceTrackingState.cpp#57,66 We can check for private browsing there. For better performance we can additionally consider stopping the entire service when both normal browsing and private browsing cookie behavior are unsupported.