1526695 - Build a UI to enable certain trackers globally

Status: RESOLVED DUPLICATE of bug 1892176

(Firefox :: Protections UI, enhancement, P3)

Description

[Asif Youssuff]

Different from Bug 1511111.

I would like to be able to whitelist certain trackers globally even though I know I am not protected by doing so.

For example, Bug 1417921 - I want to load https://en.support.wordpress.com/twitter/twitter-embeds/ and see embedded Twitter embeds.

The only way to do this if I have tracker blocking (not 3p cookies) in all windows is to disable tracking protection entirely for wordpress.com

Ideally, there would be a way in preferences and in the site shield doorhanger to enable certain trackers to enable those posts.

This might be a bit of a guessing game since it can be hard to tell which trackers are serving the content I am interested in, but it would be nice for people who want the power to unbreak sites without needing to disable tracking protection for a domain.

For my purposes, since I load Twitter in a container, I am already protected from tracking (at least as a logged in user), so enabling Twitter embeds isn't quite as unsafe as it might be.

STR:

1. Enable TP for all windows
2. Load https://en.support.wordpress.com/twitter/twitter-embeds/

What happens:

Twitter embeds do not appear.

The only way to make it appear is to disable TP for wordpress.com

Expected result:

I can choose to enable Twitter trackers on wordpress.com or globally while keeping other trackers blocked.

Comment 1

[(no longer active)]

Is the only use case viewing Twitter Embeds with TP enabled? If yes, bug 1446243 is on file for enabling that properly. I don't think we want to make it the responsibility of each and every user to configure their browser for that use case. :-)

Comment 2

[Asif Youssuff]

Well, there is the Twitter embeds and things like bug 1226498 or recaptcha -- basically, instead of Firefox having to do some kind of whitelisting automatically a la https://brave.com/script-blocking-exceptions-update/ users can choose which trackers they would like to allow.

For my own use case(s) I am often using temporary containers and first party isolation, so allowing trackers on certain first parties or globally is less of a tracking risk, and others can do the same if there were some easy way for users to do so.