But if it was only Firefox, people would simply add banners saying "Firefox is not supported." since it's only like 3% of marketshare these days.
If we are going to allow such a system then there will be natural consequences. These cookie prompts are a fools gold security theatre solution that has done nothing to improve privacy. Yet it has geneatred a mountain of UX annoyances since every single one is designed different.
Likewise blaming companies for using a limited set of cookies (see: not supercookies) is silly. There's a million legit usecases and the alternative of banning cookies is not a real solution. Stopping fingerprinting is a whole other issue.
Suggesting otherwise re: cookies is disingenuous.
The distinction is legal, not technical; so it has to be enforced by legal, not technical means.
Furthermore, there is the important distinction about multiple uses of the same data. There are uniquely identifiable cookies that are functionally required for one purpose but the site may want to use it for other purposes as well (e.g. share that data with heir "trusted partners" for targeted advertising) for which user may reasonably want to refuse permission, so a browser accepting a cookie doesn't imply such permission and something extra is required.
Itβs been how many years now and GDPR has done very little to improve anything despite the cookie prompts on websites everywhere?
At this point they are as useful as TOS (not) with the annoyance of seeing one every website.