Enable ContentClassiferEngine together with ETPengine in Nightly
Categories
(Core :: Privacy: Anti-Tracking, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox161 | --- | fixed |
People
(Reporter: timhuang, Assigned: timhuang)
References
(Blocks 1 open bug, Regressed 3 open bugs)
Details
Attachments
(5 external files)
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 1•1 month ago
|
||
This patch changes ContentClassifierService to apply
privacy.trackingprotection.content.testing.use_test_trackers_engines when it
reads the engines prefs: wherever the trackers engine is listed, test_block
is used for blocking and test_annotate for annotation, and test_block
follows the trackers scoped pref. Whatever writes the engines prefs still
decides when they are active, and test fixtures can give tracking
protection and tracking annotation separate lists, as url-classifier's
tables do.
| Assignee | ||
Comment 2•1 month ago
|
||
Once the content classifier is the engine consulted for channel
classification, the Safe Browsing tables addTestTrackers() installs are no
longer read, so the existing tracker-blocking assertions across the tree
would all fail. Publish matching content classifier lists alongside them,
gated on disable_for_channel_classifier so this stays inert until that pref
flips.
Hosts in url-classifier's tracking table and tracking annotation table are
published as the test_block and test_annotate lists, served as data: URLs,
and the service is told to use those engines in place of the trackers
engine. That keeps hosts the classic fixture annotates but never blocks off
the blocking list. The other features get Remote Settings lists.
The fixture also stands in for url-classifier's other test hooks:
addTestHostsFromPrefs() publishes the hosts a test set through the
urlclassifier.features.*.blacklistHosts and tracking table testEntries
prefs, addBuiltInTestTrackers() the entries url-classifier's tracking tables
carry built in, and hosts matching each skip URL pref become exception rules
on the matching list.
| Assignee | ||
Comment 3•1 month ago
|
||
This patch changes ProcessListChanges to repopulate the active engine lists
under the lock before it starts the rebuild, so engines that are already
built follow an engines pref change on the next classification.
Previously the lists were only refreshed once every engine rebuild's list
downloading had settled. A load issued right after changing prefs was
classified with the previous lists. Populating the already built engines
doesn't need the missing engines; they join when downloading and building
finish.
| Assignee | ||
Comment 4•1 month ago
|
||
This patch keeps url-classifier as the channel classifier, through manifest
prefs or a pushPrefEnv, for tests of what the content classifier does not
cover: url-classifier's own test directories, consent manager and anti-fraud
annotation, email tracking data collection, the entity list, the
harmful-addon feature and the url-classifier-exceptions collection.
The other tests run on the content classifier. Those that seed trackers
through url-classifier's host prefs or rely on its built-in table entries
publish the same hosts through the shared fixture, and their cleanup now
awaits the fixture so the engines are gone before the next test file.
browser_scopedTrackingProtection.js also sets the content classifier scoped
prefs for the trackers and test_block engines, and reloads between its two
loads so the first load's blocking event cannot satisfy the second check.
| Assignee | ||
Comment 5•1 month ago
|
||
This patch changes the default of privacy.trackingprotection.content.mirror.mode
to 1 and privacy.trackingprotection.urlclassifier.disable_for_channel_classifier
to true on desktop Nightly. ContentClassifierPrefMirror then drives the content
classifier from the ETP prefs, and url-classifier stops running its tracking
protection features on channels. Safe Browsing stays on url-classifier.
Until the content classifier gains equivalents, Nightly loses consent manager
and anti-fraud annotation, email tracking data collection and the entity list.
No tracker is blocked until the first engine build finishes, which on a new
profile means until the first Remote Settings sync.
Comment 7•18 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/3522517793f4
https://hg.mozilla.org/mozilla-central/rev/d2e00b72b16f
https://hg.mozilla.org/mozilla-central/rev/17cb8bae2ca4
https://hg.mozilla.org/mozilla-central/rev/75358aa55826
https://hg.mozilla.org/mozilla-central/rev/c9a8bf04e6c2
Updated•17 days ago
|
Updated•14 days ago
|
Description
•