Closed Bug 1163730 Opened 10 years ago Closed 4 years ago

tracking protection: gelio.livejournal.com images not displayed

Categories

(Web Compatibility :: Site Reports, defect, P3)

Firefox 62
x86_64
Windows 10
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mwobensmith, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [tp-ads])

User Story

yandex.ru
http://gelio.livejournal.com/79041.html  

Images not shown, because they are hosted on blocked domain "img-fotki.yandex.ru".
Component: DOM: Security → Safe Browsing
Product: Core → Toolkit
Component: Safe Browsing → Tracking Protection
Product: Toolkit → Firefox
Version: 40 Branch → unspecified
Keywords: DevAdvocacy
Priority: -- → P5
Whiteboard: tp-content
Component: Tracking Protection → Desktop
Keywords: DevAdvocacy
Priority: P5 → --
Product: Firefox → Tech Evangelism
Verified on 58.0a1 with TP enabled that images are still blocked.
Priority: -- → P5
Blocks: tpimages
No longer blocks: tp-breakage
Component: Desktop → Tracking Protection
Priority: P5 → P3
Product: Tech Evangelism → Firefox
Whiteboard: tp-content → tp-needsrepro
This is related to `tpimages` breakage #1470301

Looking at the devtools console, here are the blocked resources:

The resource at “https://kraken.rambler.ru/cnt/” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://ssp.rambler.ru/capirs_async.js” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://www.google-analytics.com/analytics.js” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://sb.scorecardresearch.com/beacon.js” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://www.googletagmanager.com/gtm.js?id=GTM-KJBSQR” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://img-fotki.yandex.ru/get/16100/30348152.1a8/0_83a0f_14435406_orig” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://stats.g.doubleclick.net/dc.js” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://www.tns-counter.ru/V13a***R%3E*sup_ru/ru/UTF-8/tmsec=lj_blogs-vis-nonad/” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://awaps.yandex.ru/0/9999/001001.gif?0-0-22690-0-&timestamp=22690&awcode=6&subsection=0” was blocked because tracking protection is enabled.[Learn More] 79041.html
The resource at “https://mc.yandex.ru/metrika/watch.js” was blocked because tracking protection is enabled.[Learn More] 79041.html

So these are the domains to test:

kraken.rambler.ru
ssp.rambler.ru
www.google-analytics.com
sb.scorecardresearch.com
www.googletagmanager.com
img-fotki.yandex.ru
stats.g.doubleclick.net
www.tns-counter.ru
awaps.yandex.ru
mc.yandex.ru

I opened the URL in a fresh browser profile (Firefox Nightly 63, uMatrix installed, normal mode) and loaded the page. The page loaded correctly. Images are displayed.
I disabled the Spoof Referrer option in uMatrix and then blacklisted:

img-fotki.yandex.ru

After this, the images were not displayed anymore.
The other resources (kraken.rambler.ru, ssp.rambler.ru, www.google-analytics.com, sb.scorecardresearch.com, www.googletagmanager.com, stats.g.doubleclick.net, www.tns-counter.ru, awaps.yandex.ru, mc.yandex.ru) didn't help.

http://prntscr.com/k7j8r1

So in conclusion:

img-fotki.yandex.ru - Advertising = [tp-ads]
User Story: (updated)
Component: Tracking Protection → Desktop
OS: Unspecified → Windows 10
Priority: P3 → --
Product: Firefox → Tech Evangelism
Hardware: Unspecified → x86_64
Whiteboard: tp-needsrepro → [tp-ads]
Version: unspecified → Firefox 62
Priority: -- → P3
Product: Tech Evangelism → Web Compatibility

Images seem to be working fine in strict mode for me now on the page.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.