[no_gravity]

Can you elaborate why it could be a good thing for users?

Not being able to reliably store data on the device means that PWAs have to send the users data over the internet and store it on an external server. I would think users rather do not like that.

I am only talking about installed PWAs here. Of course not every website should be able to avoid having its cookies deleted.

[judah]

"Good for users" was in the context of PWAs, not installed PWAs. Clearly the user's expectation is that clearing browsing data will clear data for web apps they navigate to in the browser.

Installed PWAs is another question. I suspect users will be surprised if they clear their browsing data only to discover they have to login again to Twitter, for example.

I may raise this question to the Edge Chromium team. I'm certain it's been raised before, but with Microsoft making PWAs first-class on Windows[0], this becomes a more prominent issue.

[0]: https://www.windowscentral.com/heres-how-microsoft-making-ed...

[no_gravity]

Keeping the user logged in is not the issue. A PWA can inject a unique ID into the installation in various ways.

The problem is the data. Imagine a text editor where all your text documents are gone after you cleared the data of a different app, the browser.

I wrote a fitness app as a PWA some time ago and its pretty annoying to download all the instruction videos again every time you clear your "browser data". Plus all infos about which exercises you did and when is gone for good of course.