Closed Bug 1524058 Opened 7 years ago Closed 7 years ago

Consider building a pairwise whitelist for Tracking Protection breakage

Categories

(Firefox :: Protections UI, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: englehardt, Unassigned)

References

(Blocks 1 open bug)

Details

Right now, tracking protection breakage is handled using the "Content" category of the Tracking Protection lists. That is, when a tracking domain is found to cause an unacceptable level of breakage, it is moved to the "Content" category of the Disconnect list, which is only blocked when the "Strict" version of the Disconnect list is enabled. This has a number of downsides. The main one is that severe breakage on a few popular sites may lead to a tracking domain being whitelisted on all sites.

We should instead consider pairwise whitelisting in these scenarios. That is, when breakage is discovered that would normally lead to a domain being moved from the Basic list to the Strict list, we instead add a pairwise whitelist for that domain. For example, if we discover that tracker.example breaks news.example and video.example, then we only whitelist tracker.example on those two sites when in the "Basic" mode of protection. The platform should already have support for this with our entity lists.

See Also: → 1511754

Shouldn't this be filed in one of the shavar github repos?

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Blocks: 1580351
You need to log in before you can comment on or make changes to this bug.