Open
Bug 1284985
Opened 9 years ago
Updated 3 years ago
cookies being loaded from about:newtab should use a privatebrowsing mode value >1 in the OriginAttributes instead of a temp userContextId
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox50 | --- | affected |
| firefox57 | --- | fix-optional |
People
(Reporter: baku, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [userContextId][domsecurity-backlog3][OA])
+++ This bug was initially created as a clone of Bug #1279568 +++
When we will have multiple private browsing sessions, we can use them instead using userContextId for the thumbnail generation in about:newtab.
Updated•9 years ago
|
Priority: -- → P3
Summary: cookies being loaded from about:newtab → cookies being loaded from about:newtab should use a privatebrowsing mode value >1 in the OriginAttributes instead of a temp userContextId
Comment 1•9 years ago
|
||
As offline discussion with Ehsan, this bug is blocked by bug 1271686.
And quote what Ehsan said: "enough of this stuff has already landed so whoever wants to work on this should be able to start immediately."
Depends on: 1271686
Comment 2•9 years ago
|
||
Just to clarify what we mean here, my suggestion is to load about:newtab in private mode, always, not modify anything only on cookies.
Comment 3•9 years ago
|
||
(In reply to :Ehsan Akhgari from comment #2)
> Just to clarify what we mean here, my suggestion is to load about:newtab in
> private mode, always, not modify anything only on cookies.
So about:newtab would be in a private mode that is designated for only top level about:newtab, and no other top level document loads. Correct? It would be a different private mode than the private mode used in Private Browsing Mode.
Updated•9 years ago
|
Whiteboard: [userContextId][domsecurity-backlog][OA] → [userContextId][domsecurity-backlog3][OA]
Comment 4•8 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•