Closed Bug 1301530 Opened 8 years ago Closed 8 years ago

First-party Isolation breaks Gmail

Categories

(Core :: DOM: Security, defect, P3)

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1301406

People

(Reporter: rbarnes, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [tor] [OA] [domsecurity-backlog1])

STR: 1. privacy.firstparty.isolate = true 2. Create a new container tab 3. Log into gmail.com Expected: Gmail works as normal Actual: "Gmail is having authentication problems. Some features may not work. Try logging in to fix the problem." -- and clicking the "logging in" link doesn't do anything
Is this an issue for regular gmail, or mozilla gmail with okta?
Whiteboard: [userContextId][domsecurity-*][tor][OA]
Both. I had the same issue on: 1. Normal Gmail (i.e., a gmail.com address) 2. Gmail for a domain that I own 3. Mozilla Gmail with Okta I noticed (3) first, and initially thought it was an Okta issue, but then I noticed (1) and (2).
I think this happens when we enable firstParty, if I just use a container tab it looks okay.
I believe this is because the cookies of the top-level page are not keyed by first party domain when first party isolation is enabled in e10s mode. And I have tried with non-e10s mode, the gmail works well. This problem is tracked by Bug 1301406.
Depends on: 1301406
Priority: -- → P3
Whiteboard: [userContextId][domsecurity-*][tor][OA] → [userContextId] [tor] [OA] [domsecurity-backlog1]
see comment 3, and comment 4. This doesn't related to userContextId.
Summary: First-party Isolation + Containers breaks Gmail → First-party Isolation breaks Gmail
Whiteboard: [userContextId] [tor] [OA] [domsecurity-backlog1] → [tor] [OA] [domsecurity-backlog1]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.