Closed Bug 1953716 Opened 1 year ago Closed 1 year ago

www.aerotelegraph.com - The comment section is missing from articles with ETP set to STRICT

Categories

(Web Compatibility :: Privacy: Site Reports, defect, P3)

Product:
Web Compatibility
Component:
Privacy: Site Reports
Platform:
ARM
Android
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:5, firefox136 affected, firefox137 affected, firefox138 affected)

Status:
RESOLVED FIXED
Project Flags:
Webcompat Priority P3
Webcompat Score 5
Tracking Flags:
Tracking Status
firefox136 --- affected
firefox137 --- affected
firefox138 --- affected

People

(Reporter: rbucata, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: webcompat:needs-diagnosis, 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:100
diagnosis-team:privacy

Attachments

(1 file)

STANDARD vs STRICT
1.37 MB, video/mp4
Details

Environment:
Operating system: Android 15
Firefox version: Firefox Mobile 136.0

Preconditions:

  • ETP set to Strict
  • Select the free version of the page, without ads (mit werbung) from the cookie policy to access articles

Steps to reproduce:

  1. Navigate to: https://www.aerotelegraph.com/gibt-es-bald-zwei-lothansa-dreamliner
  2. Scroll towards the end of the page and observe

Expected Behavior:
The comment section is loading

Actual Behavior:
The comment section is missing

Notes:

  • Reproduces in ETP Strict mode only
  • Reproduces in firefox-nightly, and firefox-release
  • Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/150309

Attached video STANDARD vs STRICT —
status-firefox136: --- → affected
status-firefox138: --- → affected

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

status-firefox137: --- → affected
Depends on: tp-breakage-disqus
No longer depends on: tp-breakage
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 5
Keywords: webcompat:needs-diagnosis
Priority: -- → P3
User Story: (updated)
Blocks: tp-breakage-disqus
No longer depends on: tp-breakage-disqus

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.

The shim seems to fix this! Should we mark all of the Disqus bugs as resolved, or do we intend to hold them open?

Let's close this bug with the Disqus shim(Bug 1965307).

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.

Attachment

General

Creator:
Created:
Updated:
Size: