Display remote content selectively by exact address
Categories
(Thunderbird :: Message Reader UI, enhancement)
Tracking
(Not tracked)
People
(Reporter: carbon, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
When a mail contains remote images, those are blocked by default and can be allowed with some options by pressing the button on the "To protect your privacy, ..."-bar.
Actual results:
This is fine but when you decide to view the blocked content there's a serious drawback :
You can choose to allow remote content from the sender and from the domains the images come from but there's no way to allow images selectively by taking a look on the source addresses.
Expected results:
I am thinking of something like this:
when you click the button on the "To protect your privacy, ..."-bar, besides the current options there should be an item "Decide selectively...".
Selecting this should display a list of the blocked images along with two separate buttons or checkboxes for each image. One for unblocking that source address only for this mail and one to unblock the source address permanently.
By deciding based on the information of the source address we could allow standard images but keep those with tracking information blocked.
Example:
http://someserver.com/b/1x1.png?tracking=26349234 [display in this mail] [whitelist permanently]
http://someserver.com/images/logo.png [display in this mail] [whitelist permanently]
|
||
Comment 1•3 years ago
|
||
Duplicate of one of these https://mzl.la/3IgBfMJ ?
In short, it should be easy to whitelist or blacklist addresses or parts of them so that you can block unnoticed tracking pixels, but also allow unnoticed requested images. The setup would require knowing the requested addresses before they are loaded to add them to the lists.
Basically we need something like uBlock origin for Firefox, but for Thunderbird.
|
|
||
Comment 3•4 months ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #1)
Duplicate of one of these https://mzl.la/3IgBfMJ ?
Is your request in one of these?
|
|
||
Comment 4•4 months ago
|
||
Duplicate of Bug 1960727? Provide a mechanism to determine which remote content comes from which domain
The goal of my suggestion is to allow tracking addresses (like tracking pixels) to be blocked (evident already by the URL; the feature requested in Bug 1743976 would be helpful here). At the same time, however, the email should still display well and show logos and images.
This requires the ability to see the source address of images that are being blocked within the email prior to loading, and to be able to judge and selectively allow or block them based on their address.
Regarding your question about possible duplicate bugs:
• Bug 277341 and Bug 1960727 request similar functionality, but only on a domain level, which is too broad (a single domain may provide both header images and logos as well as tracking pixels)
• The feature requested in Bug 1836595 would be part of my suggestion (the ability to selectively block temporarily or permanently)
• The feature requested in Bug 1850051 would also be part of my suggestion (a popup could show a list of remotely requested/loaded images, which can then be individually and selectively blocked either temporarily or permanently)
As an extension to my original suggestion, each blocked address should also include the option for permanent blocking, like this:
https://someserver.com/b/1x1.png?tracking=26349234 [display in this mail] [whitelist permanently] [block permanently]
https://someserver.com/images/logo.png [display in this mail] [whitelist permanently] [block permanently]
In a perfect implementation, even a custom string (with wildcards) could be entered. Example from above:
https://someserver.com/b/1x1.png?tracking=26349234 [display in this mail] [whitelist permanently] [block permanently] [block custom address]
Clicking on [block custom address] could then suggest the string "https://someserver.com/b/1x1.png?tracking=26349234", which could, for example, be modified to "https://someserver.com/*?tracking=" to make it match broader and then blocked.
Description
•