Indeed, by default file-roller will temporarily unpack files in the user's cache folder (it can in some cases fall back to the user's home directory, or a temporary directory, see https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/src/file-utils.c#L55).
Given this, I wonder whether it would be acceptable to allow firefox (and other browser snaps) to read files under @{HOME}/.cache/fr-*/, by amending an existing snapd interface.
Or could file-roller be patched to use the OpenFile method of the FileChooser portal (https://flatpak.github.io/xdg-desktop-portal/#gdbus-method-org-freedesktop-portal-FileChooser.OpenFile)? Would you mind filing a file-roller bug at https://gitlab.gnome.org/GNOME/file-roller/-/issues to request this, and link back to it here?
Indeed, by default file-roller will temporarily unpack files in the user's cache folder (it can in some cases fall back to the user's home directory, or a temporary directory, see https:/ /gitlab. gnome.org/ GNOME/file- roller/ -/blob/ master/ src/file- utils.c# L55).
Given this, I wonder whether it would be acceptable to allow firefox (and other browser snaps) to read files under @{HOME} /.cache/ fr-*/, by amending an existing snapd interface.
Or could file-roller be patched to use the OpenFile method of the FileChooser portal (https:/ /flatpak. github. io/xdg- desktop- portal/ #gdbus- method- org-freedesktop -portal- FileChooser. OpenFile)? Would you mind filing a file-roller bug at https:/ /gitlab. gnome.org/ GNOME/file- roller/ -/issues to request this, and link back to it here?