zalo.me - Blank page is displayed with ETP set to Strict
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P3)
Tracking
(firefox132 affected, firefox133 affected, firefox134 affected)
People
(Reporter: ipop, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:site-report, webcompat:tracker-blocking, Whiteboard: [webcompat-source:product][etp-pbm][etp-feature-tb-ads][etp-rc-content-blocked][fxwebdiff:diagnosed:etp-tb-fixable::ebld])
Attachments
(1 file)
|
168.59 KB,
image/png
|
Details |
Environment:
Operating system: Windows 11/10
Firefox version: Firefox 131.0.3 (release)/134
Preconditions:
- ETP set to STRICT
- Clean profile
Steps to reproduce:
- Navigate to: https://chat.zalo.me/
- Observe the behavior
Expected Behavior:
The page is displayed properly.
Actual Behavior:
A blank page is displayed.
Notes:
- Not reproducible with ETP STANDARD/turned OFF (both Normal and Private Browsing)
- Reproducible on the latest Nightly
Created from webcompat-user-report:9f6bb98b-bec6-468a-9dd4-5c9fac3a3a5b
Comment 1•1 year ago
|
||
This is caused by ETP Strict blockign "zadn.vn" tracking content.
Expected behavior but leaving Open due to high severity.
Comment 2•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 3•1 year ago
|
||
Unblocking zalo-chat-static.zadn.vn fixes the problem - the whole domain is listed on the "ads" sublist although it contains the main application itself.
Comment 4•1 year ago
|
||
This bug is related to tracker blocking and can be fixed by allowing the following trackers:
zalo-chat-static.zadn.vn
(This is an automated assessment, if this is incorrect, please needinfo.)
Updated•1 year ago
|
Comment 5•1 year ago
|
||
This bug has been fixed by a permanent intervention.
This is an automated assessment, if this bug still reproduces for you in the most recent Nightly version, please reopen.
Comment 6•8 months ago
|
||
"ETP set to STRICT" doesn't block content trackers, therefore removing tp-breakage-content from blocking tp-breakage is the correct meta bug.
Updated•8 months ago
|
Description
•