I really hate that firefox sets prefers-color-scheme: light with resistFingerprinting [0] even if the site is implemented in such a way that the color scheme selection provides no information to the server (no JS, no external resources loaded dependent on the color scheme). Even using no-preference would have been better - then the site could at least choose to make a dark theme the default.
> you're locked to en-US
Ugh, this will only lead to even more websites ignoring the Accept-Language header and just guessing based on location derived from the IP address.
Well, Chrome is removing 3rd-party cookies by next year, and they are disabled by default in Safari already (well, sort of, ITP is weird). So many problems which used to happen to very few users are now being quickly prioritized. There are lots of use cases for third party cookies (example: you have a centralized management platform for lots of websites which have unique mapped domains, and you want to be authenticated against all of them at once), so it’s not surprising that critical features can be broken. It’s very much backwards incompatible.
But I agree, overall removing 3rd party cookies is great. Though, it’s important that whatever advertisers think of next isn’t just as bad.
What does break websites is turning on anti-tracking measures. The number of times a site won’t work till I enable third party cookies shows the sad state of the web. Developers, do you only test in Chrome on Windows with default settings or something?