jgrulich added a comment.
In D28218#632902 <https://phabricator.kde.org/D28218#632902>, @ngraham wrote: > Hmm, this seems like the kind of nerdy exposing-implementation-details thing that would be problematic from a UX standpoint. I can see the use cases for wanting to open a read-only file read-write so you can actually save to it, but I think a better UX for this might be to ask the user right at the point of use, rather than putting a custom checkbox in the dialog. > > And what's the use case for wanting to open a read-write file read-only? Not sure if you understand what is this used for. With this, you open a file with permission to read it or with permission to read and write to it. It maybe doesn't make sense to open files read-only outside sandbox, but for application with limited access users actually might use it. It doesn't make a read-only file writable (as I guess you think this is about), it just allows you to specify how you want the sandboxed application to work with the opened file. The GTK file dialog has same option. By default it opens files with read and write access, but you can restrict the write access if you don't the sandboxed application to modify the file. REPOSITORY R838 Flatpak Support: KDE Portal for XDG Desktop REVISION DETAIL https://phabricator.kde.org/D28218 To: jgrulich, #plasma Cc: ngraham, apol, plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, cblack, jraleigh, zachus, fbampaloukas, GB_2, ragreen, ZrenBot, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, ahiemstra, mart
