1739975 - Images don't load on diariovasco.com with ETP - Strict enabled

Status: NEW

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

Description

[Oana Arbuzov [:oanaarbuzov]]

Attachment: StandardVsETPDisabled.png

Environment:
Browser / Version: Firefox Nightly 96.0a1 (2021-11-07)
Operating System: Windows 10 Pro

Prerequisites:
ETP - Standard enabled.

Steps to reproduce:

1. Navigate to https://www.diariovasco.com/
2. Scroll down the page.
3. Observe the images of the articles.

Expected Behavior:
The images are displayed.

Actual Behavior:
The images are not displayed.

Notes:

1. Screenshot attached.
2. The issue is not reproducible with ETP disabled.

Comment 1

[Tim Huang[:timhuang]]

This is related to the fingerprinter blocking. We've blocked static.vocento.com as a fingerprinter which leads to this issue.

Comment 2

[Tim Huang[:timhuang]]

Tom, there are several scripts from vocento.com that have been blocked because vocento.com has been classified as a fingerprinter. Whenever you have time, could you check if shim can help with this? thanks.

Comment 3

[Thomas Wisniewski [:twisniewski]]

Tim, unfortunately a lot of their scripts are being blocked as fingerprinters (jQuery, comments, video player, etc), and just getting the core site to work is pretty involved. I've managed to get it part-way there with a shim of a few window objects and bundling jQuery, but even if that all works out it will only be to get the basic page working, not video player/comments, etc. So this is effectively the same issue we have with io.vtex.com.br.

Should we do what we did for io.vtex.com.br here as well for now? (https://bugzilla.mozilla.org/show_bug.cgi?id=1713414#c12)

Comment 4

[Tim Huang[:timhuang]]

Given that adding a shim is difficult and vocento.com is in the tracking list, I think it's reasonable to also do the same thing to vocento.com.

Comment 5

[Benjamin VanderSloot [:bvandersloot]]

https://github.com/disconnectme/disconnect-tracking-protection/issues/281

Comment 6

[Thomas Wisniewski [:twisniewski]]

Nice, then i'll rename this issue to make it clear that it's strict-only now.