Bugzilla

Steven, seeing that `content-{fingerprinting|cryptomining}-track-digest256` are not enabled by default when the corresponding prefs are switchedin Gecko, what would be the correct/best GeckoView behavior for enabling fingerprinting and cryptomining protection settings (see patch)?

We do have dedicated [https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209](GeckoView anti-tracking settings) for the ad, analytics, social and content categories.

E.g., do we only want to block `content-fingerprinting-track-digest256` if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling fingerprinting protection, I would expect that all known fingerprinting sources should be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-{fingerprinting|cryptomining}-track-digest256` are not enabled by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling fingerprinting and cryptomining protection settings (see patch)?

We do have dedicated [https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209](GeckoView anti-tracking settings) for the ad, analytics, social and content categories.

E.g., do we only want to block `content-fingerprinting-track-digest256` if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling fingerprinting protection, I would expect that all known fingerprinting sources should be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-{fingerprinting|cryptomining}-track-digest256` are not enabled by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling fingerprinting and cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we only want to block `content-fingerprinting-track-digest256` if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling fingerprinting protection, I would expect that all known fingerprinting sources should be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-{fingerprinting|cryptomining}-track-digest256` are not enabled by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling fingerprinting and cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we only want to block `content-fingerprinting-track-digest256` if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling fingerprinting protection, I would expect all known fingerprinting sources to be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-{fingerprinting|cryptomining}-track-digest256` are not enabled by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling fingerprinting and cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we want to block `content-fingerprinting-track-digest256` *only* if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling fingerprinting protection, I would expect all known fingerprinting sources to be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-{fingerprinting|cryptomining}-track-digest256` are not enabled by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling fingerprinting and cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we want to block `content-fingerprinting-track-digest256` **only** if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling fingerprinting protection, I would expect all known fingerprinting sources to be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-cryptomining-track-digest256` are not enabled by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we want to block `content-cryptomining-track-digest256` **only** if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling cryptomining protection, I would expect all known cryptomining sources to be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-cryptomining-track-digest256` is not enabled (only `base-cryptomining-track-digest256` is) by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we want to block `content-cryptomining-track-digest256` **only** if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling cryptomining protection, I would expect all known cryptomining sources to be blocked, independent from my anti-tracking settings.

Steven, seeing that `content-cryptomining-track-digest256` is not enabled (only `base-cryptomining-track-digest256` is) by default when the corresponding prefs are switched in Gecko, what would be the correct/best GeckoView behavior for enabling cryptomining protection settings (see patch)?

We do have dedicated [GeckoView anti-tracking settings](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/ContentBlocking.java#209) for the ad, analytics, social and content categories.

E.g., do we want to block `content-cryptomining-track-digest256` **only** if the anti-tracking `content-track-digest256` category is also enabled?
Generally, as a user enabling cryptomining protection, I would expect all known cryptomining sources to be blocked, independent from my anti-tracking settings.

Is there a reason not to enable `content-cryptomining-track-digest256` when `privacy.trackingprotection.cryptomining.enabled` is set?