Yeah, that’s why I’m saying that the current solution does not work. It’s why I was proposing a new standard that is enforced by law and that does not depend on subjective definitions of what’s “essential” so anyone who does only want to allow certain purposes can opt in/out of certain cookies without the hassle.

If the comment really does refer to “form factor” and not “OS”, then the comment is irrelevant.

You can also run Android on a desktop form factor, the app would be then technically able to run on “desktop”. The OP’s post clearly refers to the OS, it does not matter what the form factor is, you can even run Linux on the phone (eg. PureOS).

@PumpkinSkink@lemmy.world said “reject all”, not “reject optional cookies” or “allow essential”. If the website offers a “reject all” button (which many do, even if that’s not mandated by the law), it actually does reject even the essential cookies. In my experience, the times I’ve chosen to press such button it always result on the banner showing again if you refresh the page.

And “Could be seen as” is subjective too. They could argue that having the banner, even if inconvenient, does not really break the website. They can also easily argue that since the point of the law was to get them to request consent then they are actually being even safer in terms of compliance by asking more.

Also, I still would rather have the possibility of no banners, not even the first time I open the page. The configuration from the browser following the standard could set a default for all websites and potentially avoid the popup to begin with. Then the responsibility would be with the browser, not the website.

That doesn’t work, because rejecting all cookies means it’s impossible for the page to remember whether you skipped the banner… so the result is that the banner will always show.

The real solution would be to have this be a browser / HTML standard. Similar to other permissions managed by the browser (like permission to get camera/mic, permission to send notifications, etc)… then each browser can have a way to respond to these requests for permission that we can more fully control/customize… with a UI owned by the browser that is consistent across websites and with settings that can be remembered browser-side (so the request can be automatically denied if that’s what you want).

“Essential” is still very vague. All purposes should be categorized. If used for session/identity, then it should be categorized as “session/identity”, there should not be a category defined as “essential”.

You can also make a karaoke page that does not work without access to the microphone, but still the browser has a dedicated permission request for this, it does not get mixed up into a bucket of generic “essential” permissions only because that page doesn’t work without using the microphone.

There should be a whole HTML standard similar to the Notification.requestPermission() (which requests permission to send browser notifications), but with a granular set of permissions for storage of data for different purposes.

And this should be a browser standard, not a custom popup in the logic of the website itself that will be styled differently on each page, allowing all sort of anti-patterns. I should be able to control, from the browser, what the defaults should be for each individual category of data, without having to click through every single website I visit individually. The UI to request for consent should be controlled by the browser, not by the page.