Open
Bug 1462372
Opened 6 years ago
Updated 1 year ago
[meta] Integrate anti-tracking features with developer tools
Categories
(Firefox :: Protections UI, enhancement, P3)
Firefox
Protections UI
Tracking
()
NEW
People
(Reporter: englehardt, Unassigned)
References
(Depends on 5 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
In Bug 1460058 we are experimenting with a new anti-tracking feature in Firefox. Bugs related to developer testing and devtools integration will be filed against this bug.
Comment 1•6 years ago
|
||
P5 is "WONTFIX but we'll take a patch". I believe we actually intend to work on this :)
Priority: P5 → P3
Updated•6 years ago
|
Comment 2•6 years ago
|
||
As a note on this: something that has come up with Tor Browser and FPI mode in FF before is cookie manager extensions and the cookie UI in FF not working as intended because they don't take into account the FPI Origin Attribute. If we want to consider that it might fall into this metabug.
Comment 3•5 years ago
|
||
I think there is nothing more to do here: WebExtensions are currently able to change cookieBehavior pref and to enable/disable tracking protection. They are also able to set cookie permission per website. These are the only 3 settings we use for content blocking.
Comment 4•5 years ago
|
||
(In reply to Andrea Marchesini [:baku] from comment #3) > I think there is nothing more to do here: WebExtensions are currently able > to change cookieBehavior pref and to enable/disable tracking protection. > They are also able to set cookie permission per website. These are the only > 3 settings we use for content blocking. Wrong bug? :-)
Flags: needinfo?(amarchesini)
Updated•5 years ago
|
Flags: needinfo?(amarchesini)
Reporter | ||
Comment 5•4 years ago
|
||
We've already been using this bug to track anti-tracking features other than cookie restrictions, let's make that explicit.
Summary: [meta] Integrate anti-tracking with developer tools → [meta] Integrate anti-tracking features with developer tools
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•