Closed Bug 1897379 Opened 16 days ago Closed 16 days ago

Twitter (x.com) fails to load in ETP strict and Private Browsing

Categories

(Core :: Privacy: Anti-Tracking, defect, P1)

defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox126 + fixed
firefox127 + fixed
firefox128 + fixed

People

(Reporter: pbz, Assigned: timhuang)

References

Details

(Keywords: webcompat:site-wait)

Attachments

(1 file)

Twitter doesn't load properly. Most likely because they have switched over to x.com and that domain is not on Twitter's entity list for ETP.

Work is happening in various places

(Setting webcompat:site-wait just to keep track of the outreach, not because we're actually waiting.)

See Also: → 1897357
Blocks: 1897402
Duplicate of this bug: 1897358

We're fixing this via shavar by adding x.com to the Twitter entity: https://github.com/mozilla-services/shavar-prod-lists/commit/2c57e4b34367b23c8a1ee4522903575e3f7d0c16

To speed things up we're also deploying an allow-list entry via RemoteSettings (Bug 1897402). The change has been applied, but it still takes a while to propagate via the CDN. It should show up here soon https://firefox.settings.services.mozilla.com/v1/buckets/main/collections/url-classifier-skip-urls/records

Once the shavar fix has propagated and is verified we can remove the RemoteSettings allow-list entry.

Fixed as per comment 4. Once we remove the allowlist intervention we should verify the shavar fix again.

Status: ASSIGNED → RESOLVED
Closed: 16 days ago
Resolution: --- → FIXED
Duplicate of this bug: 1897357
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: