Closed
Bug 1930140
Opened 2 years ago
Closed 2 years ago
macmagazine.com.br - Comments are not displayed with ETP set to Strict
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P3)
Tracking
(firefox132 affected, firefox133 affected, firefox134 affected)
RESOLVED
FIXED
People
(Reporter: ipop, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:site-report, Whiteboard: [webcompat-source:product])
Attachments
(1 file)
|
917.28 KB,
image/png
|
Details |
Environment:
Operating system: Windows 11/10
Firefox version: Firefox 133.0b3 (beta)/134
Preconditions:
- ETP set to STRICT
- Clean profile
Steps to reproduce:
- Navigate to: https://macmagazine.com.br/
- Click on an article
- Scroll down to the comments section
- Observe the behavior
Expected Behavior:
The comments are displayed.
Actual Behavior:
The comments are not displayed.
Notes:
- Not reproducible with ETP STANDARD/turned OFF (both Normal and Private Browsing)
- Reproducible on the latest Nightly
Created from webcompat-user-report:5b64d133-01c9-4937-ad42-1a4f86c8dd74
Updated•2 years ago
|
Blocks: tp-breakage, tp-breakage-content
Severity: -- → S3
No longer depends on: tp-breakage
Priority: -- → P3
Comment 1•2 years ago
|
||
disqus.com and its forms are on Disconnect's list of trackers we use for ETP strict, so they are blocked. This is expected behavior.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
Comment 2•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
status-firefox133:
--- → affected
Comment 3•11 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•11 months ago
|
No longer blocks: tp-breakage-content
You need to log in
before you can comment on or make changes to this bug.
Description
•