Closed Bug 1964619 Opened 1 year ago Closed 10 months ago

www.whatfinger.com - Embedded X/Twitter posts are blocked with ETP STANDARD in Private mode

Categories

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

Product:
Web Compatibility
Component:
Privacy: Site Reports
Platform:
Desktop
Windows 10
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:2, firefox138 affected, firefox139 affected, firefox140 affected)

Status:
RESOLVED FIXED
Project Flags:
Webcompat Priority P3
Webcompat Score 2
Tracking Flags:
Tracking Status
firefox138 --- affected
firefox139 --- affected
firefox140 --- affected

People

(Reporter: rbucata, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: webcompat:needs-diagnosis, webcompat:site-report, 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:10

Attachments

(1 file)

Standard vs Strict in Normal Browsing vs Private Browsing
3.18 MB, video/mp4
Details

Environment:
Operating system: Windows 10
Firefox version: Firefox 138.0

Preconditions:

  • ETP set to Standard
  • Private mode enabled

Steps to reproduce:

  1. Navigate to: https://www.whatfinger.com/home2/
  2. Scroll the page and observe

Expected Behavior:
X posts are loading

Actual Behavior:
X posts are blocked

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/155324

status-firefox138: --- → affected
status-firefox140: --- → affected
Summary: www.whatfinger.com - Embedded X/Twitter post are blocked with ETP STANDARD in Private mode → www.whatfinger.com - Embedded X/Twitter posts are blocked with ETP STANDARD in Private mode

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

status-firefox139: --- → affected
Blocks: tp-twitter
No longer depends on: tp-breakage
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 2
Keywords: webcompat:needs-diagnosis
Priority: -- → P3

This seems to be working for me now on the latest nightly. Could you confirm please?

Flags: needinfo?(rbucata)

If I accept the "Allow tracking content" for X from the shield ETP option, it works. If I remember correctly, from a previous similar issue, this is expected, so please feel free to close the issue accordingly.

Flags: needinfo?(rbucata)

Yes, we consider it fixed due to showing the smartblock embed shim allowing users to selectively unblock the tracking resource if they want to see the content.

Status: NEW → RESOLVED
Closed: 10 months 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: