> Having to get consent has made the web annoying to use because now every site needs to get your consent. I don't understand why it wasn't immediately obvious

> Having to get consent has made the web annoying to use because now every site needs to get your consent. I don't understand why it wasn't immediately obvious to browser vendors that this was going to be how web developers responded to GDPR; and that the browser vendors could/should get ahead of this degradation of the quality of the web-browsing experience by giving the user a way to do GDPR consent at the browser-chrome level by e.g. ticking a box in the browser preferences that will set a request header. (It didn't work for Do Not Track, but Do Not Track is a "request" to a malicious adversary; while "I consent to cookies, so stop prompting me" isn't.) I can only guess that browser vendors don't like GDPR, and so are avoiding implementing such a GDPR quality-of-life feature in order to ensure that users get just as annoyed by the cookie prompts as they should be, and eventually demand the law be changed.