2005278 - Reconsider useTrackingProtection variables in content process interfaces/classes

Status: ASSIGNED

(Core :: Privacy: Anti-Tracking, task, P3)

Description

[Manuel Bucher [:manuel]]

Tracking Protection is generally handled in the parent process. However we do have quite a few interfaces that expose the useTrackingProtection bit in the content-processes. This is problematic for me, because for reduce-page-protection I intent to only make the per-site settings available in the parent to keep the scope small. However, the useTrackingProtection / forceEnableTrackingProtection don't seem used at all and can be removed.

I'll investigate further whether they are really unused and can be removed or some other solution will be necessary for the reduce-page-protection project.

Comment 1

[Manuel Bucher [:manuel]]

Attachment: WIP: Bug 2005278 - Remove forceEnable bit from browsingContext

Comment 2

[Manuel Bucher [:manuel]]

Attachment: Bug 2005278 - Remove useTrackingProtection from various content-process interfaces / classes

Comment 3

[Manuel Bucher [:manuel]]

The attributes were originally added in Bug 1322576. So perhaps an android reviewer would be good.

This looks mildly related: https://searchfox.org/firefox-main/rev/7496c8515212669451d7e775a00c2be07da38ca5/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/GeckoSessionSettings.java#402-410, which is what the original code likely turned into: https://hg-edge.mozilla.org/mozilla-central/rev/162492fcf4a9#:~:text=set%20useTrackingProtection%28use%29%20%7B