Add cryptomining and fingerprinting protection options to custom content blocking preferences
Categories
(Firefox :: Settings UI, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: johannh, Assigned: johannh)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [anti-tracking])
Attachments
(1 file)
See design here:
https://mozilla.invisionapp.com/share/7TPU4WWJPUQ#/screens/339345388
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
It'd be nice to have preferences to control the visibility of each one of these. We probably don't want to start landing the code with the options visible yet.
|
Assignee | |
Comment 2•5 years ago
|
||
(In reply to :Ehsan Akhgari from comment #1)
It'd be nice to have preferences to control the visibility of each one of these. We probably don't want to start landing the code with the options visible yet.
Yeah, I agree. To get the initial work ready for QA we can probably just add simple UI preferences that hide/show the features, but in the slightly longer run I think it'd be great to have a set of features per content blocking mode defined in prefs, which the UI draws its configuration from. We might want to do a separate bug on that if we agree.
|
|
||
Comment 3•5 years ago
|
||
(In reply to Johann Hofmann [:johannh] from comment #2)
(In reply to :Ehsan Akhgari from comment #1)
It'd be nice to have preferences to control the visibility of each one of these. We probably don't want to start landing the code with the options visible yet.
Yeah, I agree. To get the initial work ready for QA we can probably just add simple UI preferences that hide/show the features, but in the slightly longer run I think it'd be great to have a set of features per content blocking mode defined in prefs, which the UI draws its configuration from. We might want to do a separate bug on that if we agree.
This sounds reasonable to me.
|
|
||
Comment 4•5 years ago
|
||
One thing to note is that the spec requires these categories to be hidden from the primary control center UI until blocking is enabled. This is different than the way we handle the current categories, so we'll likely need to do some extra work to support that in this bug.
|
|
||
Comment 5•5 years ago
|
||
(In reply to Steven Englehardt [:englehardt] from comment #4)
One thing to note is that the spec requires these categories to be hidden from the primary control center UI until blocking is enabled. This is different than the way we handle the current categories, so we'll likely need to do some extra work to support that in this bug.
Right, for Trackers in the UI we show the control centre row when they are detected. I guess you're saying we should show cryptominers/fingerprinters when they're both present and blocking has been enabled for them.
|
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Comment 7•5 years ago
|
||
TODO: The icons for cryptominers and fingerprinters are still lacking "disabled" versions. Bryan will
deliver those as soon as possible.
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
Note for localization. We are defining Fingerprinting as: Browser fingerprinting is a method of tracking users by the configuration and settings information that is visible to websites they browse, rather than traditional tracking methods such as IP addresses and unique cookies.
and
Cryptomining as: using scripts on websites that can use a computer’s resources to mine cryptocurrency without a user’s knowledge.
Pushed by jhofmann@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a424fa81316d Add cryptomining and fingerprinting protection options to custom content blocking preferences. r=ewright,flod
|
||
Comment 10•5 years ago
|
||
| bugherder | ||
Description
•