Michaël

Revoking read and write permissions is also a way for users who want to revoke them (for whatever reason) to avoid going through the command line or a graphical interface.

To clarify, this issue is more about a writing portal. It's just that using it implies read-only access for the files/folders. What needs to be discussed mainly about read access...

Apparently, with the current portal, a file can already be saved when a "directory:ro" permission is set.

Overall, this would ask every time a file needs to be saved, per application session, and even when a file has already been opened with that application. However, this would...

Can't this be done by having the file chooser remember the last folder opened for a given application?

(at least when a file was opened from it)

Indeed, what I said does not cover all cases. Another thing I said (but in another issue) is to have something that translates sandboxed file paths (`/run/user/1000/...`) to normal file...

Or given that a sandboxed file is linked to the unsandboxed one, maybe it's possible to use that link?

@adhami3310: I think this is https://github.com/flatpak/xdg-desktop-portal/pull/1045. Apps must use the new method. However, according to https://github.com/flatpak/xdg-desktop-portal/blob/main/data/org.freedesktop.portal.FileChooser.xml, "The portal implementation is free to ignore this option."

The sandbox path is translated to the host path.