Give Chromium access to xdg-download

[thatLeaflet]

The Chromium flatpak by default has access to the entire home folder. On most Linux system, this works fine as most people have their download folders in their home folder.

However, some people, like me, have their XDG download folder on secondary drives. When attempting to download anything, the download operation silently fails (as in Chromium doesn't report any issues, but the file isn't anywhere in the filesystem).

This can be worked around with using Flatseal to grant Chromium access to xdg-download, but it would be better if it had this access by default.

[Erick555]

I guess this situation is true for all xdg- paths

[thatLeaflet]

Yes, although the xdg-download path is the most important. I haven't run into any issues with the other xdg paths because the file picker portal can handle those.

The only situation that comes to mind where having full access to those other xdg paths is if someone had local websites stored in documents. In that scenario, opening the .html file would work but Chromium wouldn't have access to other sibling files, like a .css file.

[AndreiSva]

To add to this, I think giving Chromium access to the whole home directory is a bit extreme and potentially bad for security.

[Erick555]

home access is legacy stuff, you may remove it locally