Firefox and Safari have massive hard coded lists of carve outs.
There is a colossal amount of specification work to do to figure out how to make various necessary web flows possible again after removing third party cookies.
Chrome has an incredible commitment to web standards, to not throwing in arbitrary browser-specific web functionality, to going through the process of improving the web holistically. Trying to live up to that high expectation is hard, and we can see a dozen third party cookies or storage isolation concerns they're having to tackle if we go look at https://github.com/orgs/explainers-by-googlers/repositories?...
There is a colossal amount of specification work to do to figure out how to make various necessary web flows possible again after removing third party cookies.
Chrome has an incredible commitment to web standards, to not throwing in arbitrary browser-specific web functionality, to going through the process of improving the web holistically. Trying to live up to that high expectation is hard, and we can see a dozen third party cookies or storage isolation concerns they're having to tackle if we go look at https://github.com/orgs/explainers-by-googlers/repositories?...