electrek.co - Comments section not shown when expanded with Strict ETP
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:5, firefox136 affected, firefox137 affected, firefox138 affected)
People
(Reporter: ctanase, Unassigned)
References
(Blocks 2 open bugs, )
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 configuration:common affects:all branch:release user-impact-score:150
Attachments
(1 file)
|
422.80 KB,
image/png
|
Details |
Environment:
Operating system: Android 15/Windows 10
Firefox version: Firefox 136.0/138
Preconditions:
- ETP set to Strict
Steps to reproduce:
- Go to https://electrek.co/2025/03/11/tesla-cybertruck-sank-when-launching-a-jetski-after-musk-said-you-could-use-the-truck-as-a-boat/
- Scroll down the page.
- Click on the "+" button to expand the comments section.
Expected Behavior:
The comments section gets displayed.
Actual Behavior:
The comments section is not shown.
Notes:
- Reproduces in ETP Strict mode on Normal
- Reproducible with both Strict and Standard 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/150167
| Reporter | ||
Comment 1•1 year ago
|
||
| Reporter | ||
Updated•1 year ago
|
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
|
||
The severity field is not set for this bug.
:dmehic, could you have a look please?
For more information, please visit BugBot documentation.
Comment 4•1 year ago
|
||
Unblocking *://*.spot.im/*, classified as ads, unbreaks the comment section.
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.
Description
•