GNOME Bugzilla – Bug 705755
Allow applications to pass a list of allowed protocols to gtkfilechooser
Last modified: 2015-05-01 20:29:54 UTC
Currently the filechooser provides two options. 1. Allow all uris to be passed to the application and let the application handle any issues such as showing messages about unsupported protocols etc. 2. Set gtk_file_chooser_set_local_only() and only pass local addresses to the application. Option 1 means application developers must do extra work, and results in each application handling things differently such as displaying of unsupported uri messages. Option 2 leads to less than ideal outcomes. For example Firefox and Chrome currently say they don't know how to handle http addresses provided in the filechooser. Together these options make the Desktop experience very inconsistent across different applications. Suggested solution: ------------------- Allow applications to pass a list of allowed protocols to gtkfilechooser. The filechooser could then just pass allowed uris back to the application or give a consistent message that would be displayed for all applications such as:"This application does not support the smb:// protocol"
The idea is that gio / gvfs provides support for all kinds of protocols, so there's no need for apps to deal manually with this sort of filtering. There's a bug for removing the local-only option, I think.
What is the current state of this feature request? Will we see support for http(s) URLs in the file chooser dialog in the near future? Thanks for listening!
no, http is not a filesystem protocol I don't think there's anything to fix here, so I am closing this.