I would also add that even though asking for GTK3 applications like Chromium, Firefox, Thunderbird to call gtk_file_chooser_set_local_only(FALSE) seems like an easy fix, it is not:
when such applications then call for gtk_file_chooser_get_filename() (and _get_filenames), they could end up with NULL for remote files that are not fuse-mounted.
Similarly, gtk_file_chooser_get_uri() (and _get_uris) behaves differently when local-only is set or not. With local-only set, _get_uri() returns a native file:/// path, without it returns a normal uri (smb:// ...)
My understanding of the "show FUSE mounts in local-only mode" is that it helps numerous applications easily handle I/O with remote volumes without having to use GIO everywhere.
I would also add that even though asking for GTK3 applications like Chromium, Firefox, Thunderbird to call gtk_file_ chooser_ set_local_ only(FALSE) seems like an easy fix, it is not:
when such applications then call for gtk_file_ chooser_ get_filename( ) (and _get_filenames), they could end up with NULL for remote files that are not fuse-mounted.
Similarly, gtk_file_ chooser_ get_uri( ) (and _get_uris) behaves differently when local-only is set or not. With local-only set, _get_uri() returns a native file:/// path, without it returns a normal uri (smb:// ...)
My understanding of the "show FUSE mounts in local-only mode" is that it helps numerous applications easily handle I/O with remote volumes without having to use GIO everywhere.