File System entries are not deleted after browser start up

[arau0]

Describe the bug File System entries are not deleted after browser start up

To Reproduce I am not sure if that's normal behavior but in different versions of Ungoogled-Chromium I see sites, which used "File System" to have entries at chrome://settings/siteData This entries are staying after Ungoogled-Chromium is closed and open again and there are not whitelisted.

Example of site which I used and the "File System" is present https://www.theguardian.com/

Expected behavior The normal bahavior in my understanding is unless the user is whitelisted them, everything should be cleared at browser start up.

Environment (please complete the following information):

• Windows 10

[Ph0rk0z]

I can confirm this to be the case. Some site's data is left in there.

[Eloston]

What kind of data is stored in "File System"?

[Ph0rk0z]

No idea. This is what shows up...

And after browser restart:

[arau0]

@Eloston to be fair I don't know :)

@Ph0rk0z Thank you for your screenshoots.

Maybe somebody else could have appropriate information about that?

[arau0]

I am not sure if the "File System" entries at chrome://settings/siteData have any connections with the "Native File System API". There is a flag at chrome://flags/#native-file-system-api

"The Native File System API (formerly known as the Writeable Files API), is available as an origin trial in Chrome 78 (beta in September, stable in October) and later."*

"The Native File System API enables developers to build powerful web apps that interact with files on the user's local device, like IDEs, photo and video editors, text editors, and more. After a user grants a web app access, this API allows web apps to read or save changes directly to files and folders on the user's device."*

*https://web.dev/native-file-system/

[PF4Public]

This is an old issue, that didn't show much activity recently — closing. If you have any more information to add, let us know.