Browser Partition
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
Many existing APIs were not "partition-aware" and result in leakages that need to handled in a "whack-a-mole" approach. One example is the :visited tags which were recognized as a leak in 2011, but were not addressed until 2023 because the solution caused some functionality of the coloring of links to be disabled. Only then was a solutions proposed to prevent leakage of this information to any web site.
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.
