Closed
Bug 1300702
Opened 8 years ago
Closed 8 years ago
Reload page after toggle privacy.firstparty.isolate pref
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: allstars.chh, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tor][domsecurity-backlog1][tor-standalone])
The firstPartyDomain is calculated in the top-level document and propagate to the sub-docshells, which means if we turn on/off the pref, the already opened webpages still use the same data-jar. This somehow may confuse users, as they will think the opened webpages will use a different data-jar after toggling the pref. But reloading immediately could possibly interrupt some user flow of web pages. For example, I am writing some form in other tab, and turn on the pref in another tag. So we need a good UI to tell user about this
Reporter | ||
Updated•8 years ago
|
Whiteboard: [tor] → [tor][domsecurity-backlog1]
Comment 1•8 years ago
|
||
Do we have the similar issue in Containers? What's the behavior of Containers while turning on/off the preference?
Updated•8 years ago
|
Priority: -- → P3
Comment 2•8 years ago
|
||
I tried Tor browser. If I switch the preference "privacy.thirdparty.isolate", the existing tabs still use the data-jar without double-keys. There was no reloads or UI, so I think we don't have to do this for Tor uplift. But we can still do this if we think this is a serious problem.
Updated•8 years ago
|
Whiteboard: [tor][domsecurity-backlog1] → [tor][domsecurity-backlog1][tor-standalone]
Reporter | ||
Comment 3•8 years ago
|
||
Tor doesn't support this either.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•