www.gls-info.nl - Blank page with Strict ETP
Categories
(Web Compatibility :: Privacy: Site Reports, defect)
Tracking
(firefox133 affected, firefox134 affected, firefox135 affected)
People
(Reporter: ctanase, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:site-report, webcompat:tracker-blocking, Whiteboard: [webcompat-source:web-bugs][fxwebdiff:diagnosed:etp-tb-fixable::ebld])
Environment:
Operating system: Linux / Windows 10
Firefox version: Firefox 132.0/133/135
Preconditions:
- Strict ETP enabled
Steps to reproduce:
- Go to https://www.gls-info.nl/
- Observe the page.
Expected Behavior:
The page is loaded.
Actual Behavior:
The page is blank.
Notes:
- Reproduces in ETP Strict mode only
- In PBM reproduces with both Strict and Standard ETP but not with ETP OFF
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/144519
| Reporter | ||
Updated•10 months ago
|
| Reporter | ||
Updated•10 months ago
|
Comment 1•10 months ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Reliance on cookiebot.com seems to be the culprit.
Comment 3•10 months ago
|
||
Also reproduces on Firefox Focus for Android.
When I visit gls-info.nl in Private Browsing mode in Firefox desktop, the page is blank and the console shows:
The resource at “https://consent.cookiebot.com/uc.js” was blocked because content blocking is enabled.
Cookie “_cookie_test” has been rejected for invalid domain.
Cookie “_cookie_test” has been rejected for invalid domain.
ERROR TypeError: window.__tcfapi is not a function
initializeCookiebot https://gls-info.nl/main-GF2GNVTS.js:643
When I open the console and run the following snippet: window.__tcfapi = () => {} at page load but before script execution, the website seems to work.
Comment 4•7 months ago
|
||
This bug is related to tracker blocking and can be fixed by allowing the following trackers:
consent.cookiebot.com
(This is an automated assessment, if this is incorrect, please needinfo.)
Comment 5•7 months ago
|
||
Automated diagnoses shows this bug was caused by blocking one of the consent managers on the CMP list that were erroneously also listed on the analytics list. This has been fixed and the site should now work in private browsing mode as well as ETP-Strict. If any of these modes still fail, please reopen the bug.
Updated•6 months ago
|
Description
•