Tracking-annotation should use strict list always
Categories
(Core :: Privacy: Anti-Tracking, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: baku, Assigned: baku)
References
Details
Attachments
(1 file)
The difference between strict and basic tracking list is about the content-tracking table. In this bug, I would like to use the content-tracking table always, and to have a separate pref to decide when we want to consider it to detect trackers.
If a channel's URL is found in the content-tracking list, it will be classified using nsIHttpChannel::ClassificationFlags::CLASSIFIED_TRACKING_CONTENT. But nsIHttpChannel::IsTrackingResource() would return false if we are in basic-tracking-list mode.
Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 3•6 years ago
|
||
bugherder |
Comment 4•6 years ago
|
||
backout bugherder uplift |
Backed out 4 changesets (Bug 1541238, Bug 1542069, Bug 1533363) for build bustages - missing Bug 1536488
https://hg.mozilla.org/releases/mozilla-beta/rev/ca196717df07
Updated•6 years ago
|
Comment 5•6 years ago
|
||
(In reply to Bogdan Tara[:bogdan_tara] from comment #4)
Backed out 4 changesets (Bug 1541238, Bug 1542069, Bug 1533363) for build bustages - missing Bug 1536488
https://hg.mozilla.org/releases/mozilla-beta/rev/ca196717df07
Hi Baku, can you uplift this to beta for Bug 1541238, Bug 1542069, and Bug 1533363?
Assignee | ||
Comment 6•6 years ago
|
||
Tanvi, what do you think about this uplift? I suspect it could break some shield studies.
Updated•6 years ago
|
Comment 7•6 years ago
|
||
We are no longer going to try to uplift the other bugs so we don't need to uplift this one.
Description
•