Since we don't want to prompt users AT ALL about Tracking Protection in the pseudo-control, we can't rely on built-in Tracking Protection, which has its own onboarding sequence.
I have therefore changed the pseudo-control treatment to set built-in Tracking Protection OFF globally, just like the experimental treatment branches "fast" and "private" and used the same approach to re-implement Tracking Protection via the WebRequest.onBeforeRequest event. I just had to make sure that UI is only added when a resource is blocked for the "fast" and "private" branches only.
Before
The first time the user visits a site with at least one resource blocked:
After
The first time the user visits a site with at least one resource blocked:
Since we don't want to prompt users AT ALL about Tracking Protection in the pseudo-control, we can't rely on built-in Tracking Protection, which has its own onboarding sequence.
I have therefore changed the pseudo-control treatment to set built-in Tracking Protection OFF globally, just like the experimental treatment branches "fast" and "private" and used the same approach to re-implement Tracking Protection via the WebRequest.onBeforeRequest event. I just had to make sure that UI is only added when a resource is blocked for the "fast" and "private" branches only.
Before
The first time the user visits a site with at least one resource blocked:
After
The first time the user visits a site with at least one resource blocked: