Closed Bug 1559969 Opened 1 year ago Closed 1 year ago

Move cryptomining blocking to the Standard mode of content blocking

Categories

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

task
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla69
Tracking Status
firefox69 --- verified

People

(Reporter: englehardt, Assigned: englehardt)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Cryptomining blocking is currently set for Strict in Beta and Release. We should move it to Standard for Firefox 69 release.

Type: defect → task
Blocks: 1560184
No longer blocks: 1560184
Assignee: nobody → senglehardt
Keywords: checkin-needed

Pushed by ccoroiu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d8a3b12ffb3d
Enable cryptomining blocking by default. r=baku

Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69

The strict category pref still includes cryptomining: https://searchfox.org/mozilla-central/rev/da3f3eaaacb6fb344fd21ac29ace2da0e33f12d3/browser/app/profile/firefox.js#1608.

Was this the correct fix for the bug?

Flags: needinfo?(senglehardt)
Flags: needinfo?(ewright)

(In reply to :Ehsan Akhgari from comment #4)

The strict category pref still includes cryptomining: https://searchfox.org/mozilla-central/rev/da3f3eaaacb6fb344fd21ac29ace2da0e33f12d3/browser/app/profile/firefox.js#1608.

Was this the correct fix for the bug?

Yes, this is correct. "move" is perhaps not the best choice of words. Cryptomining blocking should be enabled in both strict and standard. We wouldn't want standard to block something which is not also blocked in strict.

Flags: needinfo?(senglehardt)
Flags: needinfo?(ewright)

Thanks for checking!

Flags: qe-verify+
Flags: needinfo?(ciprian.georgiu)

This bug is verified as fixed on Beta 69.0b5. I've checked that Cryptomining is moved to Standard accordingly, across platforms: Windows 10 x64, macOS 10.13 and Ubuntu 18.04 x64.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
Flags: needinfo?(ciprian.georgiu)
You need to log in before you can comment on or make changes to this bug.