Closed
Bug 1955195
Opened 1 year ago
Closed 1 year ago
www.muylinux.com - Comments section does not load with Strict ETP
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P3, Webcompat Score:4)
RESOLVED
FIXED
People
(Reporter: ctanase, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, webcompat:tracker-blocking, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:feature-broken-minor configuration:common affects:all branch:release user-impact-score:50
Environment:
Operating system: Linux/Windows 10
Firefox version: Firefox 136.0/138
Preconditions:
- ETP set to Strict
Steps to reproduce:
- Go to https://www.muylinux.com/2025/03/17/gimp-3-descarga/
- Scroll down the article.
- Click on "Click para comentar" button.
Expected Behavior:
The comments are displayed.
Actual Behavior:
The button disappears and nothing else happens
Notes:
- Reproduces in ETP Strict mode only in Normal
- Reproduces with both Standard and Strict ETP in PBM (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/150837
Same here, with Firefox ESR 128.8 from Mageia 9 Linux Plasma Kde.
If I can change to Standar mode, the comments in "muylinux.com" appears.
Blocks: tp-breakage-disqus
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 4
No longer depends on: tp-breakage
Keywords: webcompat:platform-bug
Priority: -- → P3
Updated•1 year ago
|
Keywords: webcompat:tracker-blocking
Comment 2•1 year ago
|
||
Moving to S4 as this bug does not fulfill the criteria for an exception in private browsing mode or ETP-Strict. This will likely be fixed with a shim.
Our SmartBlock UI opt-in feature now supports Disqus, displaying a placeholder where content has been blocked. This bug can be closed.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•