GNOME Bugzilla – Bug 320690
GtkFileChooser should check writability
Last modified: 2018-02-10 03:42:50 UTC
If the file or the directory it's in is not writable, it's no use prompting the user whether he wants to replace it!
*** Bug 327708 has been marked as a duplicate of this bug. ***
My text from the duplicate bug, because it's not exactly what this bug talks about: " I think the FileChooser should not allow the user to specify a path in a read-only directory. It should tell the user that he does not have rights to add files to that directory and let him choose a different path instead. Otherwise, the application has to do this, and applications will do it inconsistently. "
Bug #137515 is kind of a duplicate of this too. It suggests graying-out read-only locations.
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue for it.