Or they could have mandated cookie consent but require it to be handled by the browser, not the site (page and server). Define some standardized cookie descript

Or they could have mandated cookie consent but require it to be handled by the browser, not the site (page and server). Define some standardized cookie description format, get it to the browser, and let it handle prompting the user for consent. Any cookie the user doesn't consent to is dropped instead of being stored. Benefits: (1) Don't have to trust the site to honor your consent. (2) Sites won't try dark UI patterns (because they're not building the UI). (3) More standardized UI because instead of each site inventing their own, they all use the browser's UI. (4) Less tedium for the user. Browser can let the user choose defaults for the cookie consent dialog. Or define rules to handle certain choices automatically. And, if you can standardize categories (performance cookies, advertising cookies, etc.), then you can apply defaults and rules to those too. (5) Web developers' jobs are easier. Just maintain and serve a cookie description data file. And of course be prepared to live without certain cookies. Yes, this is extra work for the developers of browsers themselves. But it would be worth it. And apparently they're already spending engineering resources on cookie consent anyway.