https://bugs.kde.org/show_bug.cgi?id=398446
--- Comment #4 from Nate Graham <n...@kde.org> --- (In reply to a.saoutkin from comment #3) > Hopefully in this case if the file opens in a KIOFuse mount they'll simply > use the "save" functionality and hence won't run into this at all. If they > choose to use "Save As" hopefully the dialog is smart enough to choose where > the current file is currently saved (i.e. in the KIOFuse mount somewhere). Generally this is true. > If not, I guess they're on their own. However, for dialogs that do exhibit > this behaviour, I don't think we want to put up a patch upstream displaying > the KIOFuse mount as a location, it'll be better if we patched it such that > the behaviour in my paragraph above occurs, thoughts? Yes, in the cases where the above doesn't work, it should be fixed. However what happens if, in the above use case, the user navigates somewhere else and realizes they need to get back to the FUSE mount location? They can use the back button, but having it visible in the Places panel too would be a nice touch IMO. -- You are receiving this mail because: You are watching all bug changes.
