Yep... look at just the cookie prompts,.. they suck, the users just click "agree", and if they want to disagree, they have to invest sometimes literal minutes, to unheck all the cookie providers.
The default should be always to delete everything after a website/tab is closed. Want to store a login? Set up a button next to the url bar to enable persistant storage for that specific webpage, and you're done.
Almost every web page demands a login today...you want to be the browser vendor dealing with the literal billions of users lodging complaints because they forget to click the save button before closing a tab and now they have to log in again?
I think it would work well if installing web apps as PWAs, with the PWAs’ webviews being sandboxed and backed by their own entirely separate storage, cookies, etc, was what enabled persistent features. It would eliminate several types of fingerprinting in one fell swoop.
Cookie dialogs are set up that way because they know people will agree. A website I visit regularly (and have a subscription for, soundonsound.com), had a very easy cookie dialog. But no longer. Now you must accept their cookies (it’s quite a lot, really). One can only guess why.
People would then just be trained to always click that button, even preemptively, as a magical fix button. And we'd get a whole new Youtubey "remember to smash that button!" but for every website.
The default should be always to delete everything after a website/tab is closed. Want to store a login? Set up a button next to the url bar to enable persistant storage for that specific webpage, and you're done.