Closed Bug 1977066 Opened 7 months ago Closed 6 months ago

Strict ETP features list missing cryptominers

Categories

(Core :: Privacy: Anti-Tracking, defect)

defect

Tracking

()

VERIFIED FIXED
143 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox-esr140 --- verified
firefox140 --- wontfix
firefox141 --- verified
firefox142 --- verified
firefox143 --- verified

People

(Reporter: jscher2000, Assigned: wwen)

References

(Regression)

Details

(Keywords: regression)

Attachments

(4 files)

Bug 1956556 changed the feature string for cryptomining protection from "cm" to "cryptoTP" in various files, but one file was overlooked: the privacy.js file that configures the lists shown on the Settings page.

This affects the Strict mode list because the rulesArray for Strict mode is built from the value of browser.contentblocking.features.strict, which uses the new string. Ref. https://searchfox.org/mozilla-central/source/browser/components/preferences/privacy.js#1403

On the other hand, the Standard mode rulesArray is built using the old string:

        rulesArray.push(
          defaults.getBoolPref(
            "privacy.trackingprotection.cryptomining.enabled"
          )
            ? "cm"
            : "-cm"
        );

https://searchfox.org/mozilla-central/source/browser/components/preferences/privacy.js#1469

Then irrespective of source, the rulesArray is parsed using the old string, which causes the miss for the Strict mode list:

          case "cm":
            document.querySelector(selector + " .cryptominers-option").hidden =
              false;
            break;
          case "-cm":
            document.querySelector(selector + " .cryptominers-option").hidden =
              true;
            break;

https://searchfox.org/mozilla-central/source/browser/components/preferences/privacy.js#1548

This discrepancy was identified as a source of alarm by a Redditor: https://old.reddit.com/r/firefox/comments/1ly588i/no_mention_of_cryptominers_in_strict_tracking/

Seems that privacy.js needs to be updated to use the new string.

Set release status flags based on info from the regressing bug 1956556

:wwen, since you are the author of the regressor, bug 1956556, could you take a look?

For more information, please visit BugBot documentation.

Assignee: nobody → wwwenwilliam
Status: NEW → ASSIGNED

Mark, could that be in our planned dot release? Thanks

Flags: needinfo?(mstriemer)
Flags: needinfo?(wwwenwilliam)

Set release status flags based on info from the regressing bug 1956556

Pushed by wwwenwilliam@gmail.com: https://github.com/mozilla-firefox/firefox/commit/c02b677b2cfa https://hg.mozilla.org/integration/autoland/rev/2db66ca72576 Change missed "cm" strings to "cryptoTP". r=anti-tracking-reviewers,webdriver-reviewers,timhuang
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch

The patch landed in nightly and beta is affected.
:wwen, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(wwwenwilliam)
Attachment #9504193 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined: The crytominer blocking won't be configured properly if users changes ETP settings
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: None
  • Risk associated with taking this patch: Low
  • Explanation of risk level: The change is small.
  • String changes made/needed: None
  • Is Android affected?: no
Attachment #9504193 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Flags: needinfo?(mstriemer)

Please add Release and ESR140 requests also when you get a chance.

Flags: needinfo?(wwwenwilliam) → needinfo?(tihuang)
Attachment #9504937 - Flags: approval-mozilla-release?

firefox-release Uplift Approval Request

  • User impact if declined: The crytominer blocking won't be configured properly if users changes ETP settings
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: None
  • Risk associated with taking this patch: low
  • Explanation of risk level: The change is small.
  • String changes made/needed: None
  • Is Android affected?: no
Attachment #9504938 - Flags: approval-mozilla-esr140?

firefox-esr140 Uplift Approval Request

  • User impact if declined: The crytominer blocking won't be configured properly if users changes ETP settings
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: None
  • Risk associated with taking this patch: Low
  • Explanation of risk level: The change is small.
  • String changes made/needed: None
  • Is Android affected?: no
Flags: needinfo?(tihuang)
Attachment #9504938 - Flags: approval-mozilla-esr140? → approval-mozilla-esr140+
Attachment #9504937 - Flags: approval-mozilla-release? → approval-mozilla-release+
Component: Settings UI → Privacy: Anti-Tracking
Product: Firefox → Core
QA Whiteboard: [qa-triage-done-c143/b142] [qa-ver-needed-c143/b142]
Flags: qe-verify+
QA Contact: cgeorgiu

I've reproduced this issue using an affected Nightly build (2025-07-12) on Win 11.

The issue is verified as fixed on the fixed builds: 143.0a1, 142.0, 141.0.3 and 140.2.0 Esr.

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triage-done-c143/b142] [qa-ver-needed-c143/b142] → [qa-triage-done-c143/b142] [qa-ver-done-c143/b142]
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: