Fixes #2424 Enhanced Tracking Protection

[keianhzo]

Fixes #2424 Enhanced Tracking Protection

[keianhzo]

There are a few common issues with the WebXR settings PR:

• Dialog not closed when switching windows
• Dialog not closed when clicking on the button again
• Hide buttons in the content feed.

I'll fix those when I rebase this one with the pending PRs.

[bluemarvin]

I think we only want one or the other set at one time?

[droeh]

These are independent, actually. antiTracking controls what content gets blocked when GeckoSessionSettings.useTrackingProtection is true, while enhancedTrackingProtectionLevel controls what cookies get blocked when our cookie behavior is ACCEPT_NON_TRACKERS.

[bluemarvin]

The way I understood what was explained to me is that we only want one active at a time. If we are blocking cookies we don't want to be blocking content as that is the purpose of ETP, it just blocks the tracking cookies and the content is all loaded which reduce breakage, where content blocking is more strict but also causes more breakage.

[bluemarvin]

These are independent, actually. antiTracking controls what content gets blocked when GeckoSessionSettings.useTrackingProtection is true, while enhancedTrackingProtectionLevel controls what cookies get blocked when our cookie behavior is ACCEPT_NON_TRACKERS.

@droeh I guess I'm still confused, I don't see GeckoSessionSettings.useTrackingProtection() except when the session is created. Does this mean it never gets turned off?

[droeh]

Sorry for the slow reponse, I'm not used to getting work mail from github!
There are cases where you might want to leave ETP and TP both enabled, for example you may want to enable TP only for one category and ETP for the rest. In general they are only exposed in UI mutually exclusively, though (eg as "Standard" and "Strict" in desktop).

And yeah, I missed that, but you definitely need to update GeckoSessionSettings.useTrackingProtection() to control TP, and do it for every session. (Yes, that sucks, it's on the list of things to change in the API.)

I'll keep an eye on github mail and respond quicker if you have any more questions.

[droeh]

The tracking protection related stuff looks good to me.

[droeh]

These are independent, actually. antiTracking controls what content gets blocked when GeckoSessionSettings.useTrackingProtection is true, while enhancedTrackingProtectionLevel controls what cookies get blocked when our cookie behavior is ACCEPT_NON_TRACKERS.

[bluemarvin]

@keianhzo droeh says this is the site to use for testing: https://senglehardt.com/test/trackingprotection/test_pages/

[keianhzo]

@bluemarvin @droeh I've rebased and removed all redundant code. I've been testing with the site above and I think the results are good, also are the sames as Fenix.

[bluemarvin]

Seems to work from my testing. It would be nice if we could do a v2 where the shield changed colors when it actually blocks some thing and then clicking on that would give more details on what was blocked.

[bluemarvin]

Okay, I'm not sure it is actually working:
I turned off tracking protection:

But it says tracking protection is still on and cookies are still getting blocked:

[bluemarvin]

I wonder if we should even show the shield if tracking protection is turned off.

[keianhzo]

@bluemarvin Regarding:

But it says tracking protection is still on and cookies are still getting blocked:

I see the same behavior in Fenix, maybe @droeh can clarify.

And regarding:

I wonder if we should even show the shield if tracking protection is turned off.

I'll look into that tomorrow

[keianhzo]

@bluemarvin updated with hiding the tracking protection icon if disabled.

[bluemarvin]

Will file follow up for GV issue https://bugzilla.mozilla.org/show_bug.cgi?id=1625210

[bluemarvin]

Follow up issue #3053