Closed
Bug 1639154
Opened 2 years ago
Closed 2 years ago
Isolate network cache per first-party when privacy.partition.network_state is set to true
Categories
(Core :: Privacy: Anti-Tracking, task)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
FIXED
mozilla78
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: baku, Assigned: baku)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
No description provided.
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → amarchesini
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•2 years ago
|
||
Depends on D75921
Pushed by amarchesini@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/66abd66fc467 Isolate network cache per first-party when privacy.partition.network_state is set to true - part 1 - implementation, r=mayhemer,necko-reviewers https://hg.mozilla.org/integration/autoland/rev/7e53b5398797 Isolate network cache per first-party when privacy.partition.network_state is set to true - part 2 - tests, r=mayhemer
|
||
Comment 4•2 years ago
|
||
Excuse my ignorance, but with these patches, such as this one and Bug 1639247, do they isolate the "same" as FPI (privacy.firstparty.isolate) or is it different? (note: FPI & dFPI in Bug 1631676). In other words, when flipped on, will they causes any conflicts or always be the most restrictive if there is a difference in approach? TIA
|
||
Comment 5•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/66abd66fc467
https://hg.mozilla.org/mozilla-central/rev/7e53b5398797
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•