Difference between revisions of "Browser Partition"
(→Where to build the partition?) |
(→Problems) |
||
| Line 9: | Line 9: | ||
===Where to build the partition?=== | ===Where to build the partition?=== | ||
The current plan in Google and Chromium is to partition the browser based on the "top-level domain". | The current plan in Google and Chromium is to partition the browser based on the "top-level domain". | ||
| + | |||
| + | ===The Legacy APIs=== | ||
| + | May existing API base not "partition-aware" and result in leakages that need to handled in a "whack-a-mole" approach. | ||
==Solutions== | ==Solutions== | ||
Revision as of 14:22, 27 June 2023
Contents
Full Title or Meme
The original browser were limited the lack of an state between screens. Adding state has required a means to partition that state to the appropriate sources.
Context
Google Chrome is going ahead with strong tracking protection and Firefox and Safari already have this. -miketaylr@chromium.org (2023-04-25_
Problems
Where to build the partition?
The current plan in Google and Chromium is to partition the browser based on the "top-level domain".
The Legacy APIs
May existing API base not "partition-aware" and result in leakages that need to handled in a "whack-a-mole" approach.
Solutions
Cookies
All major Browsers have deprecated the use of Third Party Cookies while some Browsers still allow them within partitions with names like First-Party Sets. Click that link for details. Some Browsers just ban all Third Party Cookies with no work-around like that.
