Open Bug 1772545 Opened 2 years ago Updated 1 year ago

Revert partitioning skiplist intervention for login.live.com

Categories

(Core :: Privacy: Anti-Tracking, task, P3)

task

Tracking

()

People

(Reporter: pbz, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Breakage bug for which this skiplist entry is being added (also add in "Depends on"): Bug 1771258.

Tracking protection feature(s) to be skiplisted: partitioning-exempt-urls

Pattern to be skiplisted: *,https://login.live.com

Timeline of intervention (See our timeline policy): 3 months

Planned steps to resolve intervention (e.g., outreach, technical fixes, policy fixes): We are planning to ship an anti-tracking shim through our webcompat addon that will not require skiplisting. Once that reaches all platforms (desktop and mobile) we will remove this intervention.
We also plan to reach out to the vendor to notify them of the breakage, for them to address the issue, e.g. via calling the Storage Access API.

Severity: normal → S3
Assignee: nobody → pbz
Status: NEW → ASSIGNED

Keeping this open for the more recent Office breakages.

Depends on: 1747895, 1747889
No longer depends on: 1771258
Assignee: pbz → nobody
Status: ASSIGNED → NEW

Sorry meant to NI here to see if the entry can be removed. See https://bugzilla.mozilla.org/show_bug.cgi?id=1747889#c10

Flags: needinfo?(tihuang)
Flags: needinfo?(tihuang)

We're working in reverting this entry. We've removed it for pre-release channels (Nightly, Beta), with release to follow once we are confident this isn't causing significant website breakage.

(In reply to Tim Huang[:timhuang] from comment #3)

We still need this entry per https://bugzilla.mozilla.org/show_bug.cgi?id=1747889#c12

With the allow-list entry removed this does indeed break again. It needs to be fixed from Microsoft side. It also breaks in Safari and Brave.

The entry removal will happen from Firefox 118 in the release channel. Once Firefox gets updated to 118, the entry will no longer apply.

You need to log in before you can comment on or make changes to this bug.