Tracking Protection is generally handled in the parent process. However we do have quite a few interfaces that expose the useTrackingProtection bit. 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.
Bug 2005278 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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.