1800922 - Consider updating the console messages and network devtools panel messages for "content blocking"

Status: NEW

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

Description

[Thomas Wisniewski [:twisniewski]]

For instance, load a fresh nightly profile and visit https://www.livescore.com/en/

Despite being in standard ETP mode, ads are being blocked on that page, and this message appears in the console:

The resource at “https://www3.doubleclick.net/” was blocked because content blocking is enabled.

This appears to be because of Email tracking protection is kicking in, and it would be very good to know that so users (like our webcompat team) don't wonder if they have left strict ETP on, and then wonder what's wrong when it's clearly still off.

Tweaking the messages to explain the reason/list which triggered the blockage would reduce the confusion here.

Likewise adjusting this message (which can be seen on the same URL on Firefox release, perhaps after a page-refresh) would be useful:

Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled.

Tweaking the phrasing to say "cookie blocking" rather than "content blocking" might be a good idea, so users don't wonder if other types of content are being blocked.

And of course, also showing the list/reason that a given request was blocked (in the devtools) would be useful. Right now, there is no indication that it was blocked by email tracking protection, all one sees in the network tab of the devtools for the request is that it has been "blocked".