GNOME Bugzilla – Bug 136501
ftp:// links should open in nautilus by default
Last modified: 2016-09-12 01:17:05 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: epiphany Severity: enhancement Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: ftp:// links should open in nautilus by default Bugzilla-Product: epiphany Bugzilla-Component: General Bugzilla-Version: unspecified Description: Please describe your feature request: Especially in GNOME 2.5, it makes perfect sense for epiphany to open ftp:// link in nautilus windows by default, similar to how mailto:// links are opened in evolution. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-07 18:12 ------- The original reporter (bpsn74@mizzou.edu) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, marco@gnome.org.
I bet this is going to be controversial but ihmo worth strong consideration. The only thing I'm worried about is pretty bad ftp support in nautilus (is it still bad ?).
Confirming as enhancement. Need to find out how good Nautilus's FTP handling is (like authentication, speed, uploads/downloads etc.). Note that Internet Explorer (optionally) uses Windows Explorer for FTP sites, although it's hopelessly slow. Also need do decide how to handle the case where ftp sites are in frames or iframes. Testcase below. IE embeds Windows Explorer.
Created attachment 25344 [details] Example of embedded FTP
Just realized this is already possible. Just configure an ftp service in Applications->Desktop Preferences->Advanced->File types. Then let us know how well it works ;)
There doesn't seem to be a way to configure nautilus to open a specified url?
How could this be fixed? Also, what would happen with ftp downloads if we made ftp open in nautilus? Is there a way to configure moz only to open ftp _directory_ links in the ext handler?
Mass-moving Target 1.4 -> 1.6 because of feature and UI freeze. Sorry for the bugspam, search for "mass-move-1.4-1.6" to filter all of it.
Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o
Mass-moving bugs from Target Milestone: 1.6 to 1.8 because of feature, UI and string freeze.
Target: 1.8 -> 1.10 due to feature and UI freeze.
i drag an drop an ftp link from epiphany to my desktop. it was just a little file download, but something bother me, with a dialog. it asked, if i want to connect annonymous our with a user login. maybe this question will confuse people, who didn't know much about ftp and just want download a file which is by chance on a ftp server...
Better than only ftp:// links, Epiphany should open Nautilus (or the file manager set as the default one) when trying to open a file:/// link. Integrating Nautilus in Ephy?
-> 1.12 due to feature and UI freeze.
This seems to be more interesting now as webkit seems to not support ftp:// protocol :-/ Thanks a lot
There's 2 problems: 1) Epiphany doesn't even try to mount the location for itself 2) It fails to load the page even after mounting the location by hand: Unable to load page Problem occurred while loading the URL ftp://dd-wrt.com/others/eko/BrainSlayer-V24-preSP2
Considering this a major bug instead of just an enhancement.
I'm reasonably sure with all the recent developments in Nautilus and Epiphany we just want to open ftp:// links inside the browser now (like other browsers do). Closing.
Xan, I guess you know what you're talking about more than I do, but in Epiphany 3.5.4, FTP links don't even work, and on previous versions FTP links only worked read-only. However, FTP now works flawlessly in Nautilus, so it seems to me there is now *no* good reason to open an FTP link in Epiphany... So could you please elaborate what you wrote in your last comment?
(In reply to comment #19) > Xan, I guess you know what you're talking about more than I do, but in Epiphany > 3.5.4, FTP links don't even work, and on previous versions FTP links only > worked read-only. However, FTP now works flawlessly in Nautilus, so it seems to > me there is now *no* good reason to open an FTP link in Epiphany... > > So could you please elaborate what you wrote in your last comment? So, two things: - Epiphany should *really* support this. The fact that it doesn't shouldn't drive design. - My impression is that nautilus is being simplified and streamlined to work well in a reduced set of cases, and interacting correctly between FTP servers/Web/your disk does not sound like one of those. So I think we should just make this work OK in ephy and be done with it.
OK. Then I've reported bug #681881 about the lack of FTP features in current Epiphany.
(In reply to comment #20) > (In reply to comment #19) > > Xan, I guess you know what you're talking about more than I do, but in Epiphany > > 3.5.4, FTP links don't even work, and on previous versions FTP links only > > worked read-only. However, FTP now works flawlessly in Nautilus, so it seems to > > me there is now *no* good reason to open an FTP link in Epiphany... > > > > So could you please elaborate what you wrote in your last comment? > > So, two things: > > - Epiphany should *really* support this. The fact that it doesn't shouldn't > drive design. > - My impression is that nautilus is being simplified and streamlined to work > well in a reduced set of cases, and interacting correctly between FTP > servers/Web/your disk does not sound like one of those. > > So I think we should just make this work OK in ephy and be done with it. We already launch other URL schemes in their handlers (clicking on a magnet link launching bittorrent, launching an itms URL has rhythmbox show up, rtsp/rtmp will show up in totem, etc.). I don't see what's different here given that Epiphany doesn't support FTP (yet), and that that would allow users to use a specialised application to handle FTP if they wanted to (just change the x-scheme-handler/ftp mime handler).
I don't really think it's a good idea to fully reimplement FTP in Epiphany. If read-only, http-directory-like support is what we aim to offer, I believe that letting Nautilus do it for us is a far superior idea.
(In reply to comment #23) > I don't really think it's a good idea to fully reimplement FTP in Epiphany. If > read-only, http-directory-like support is what we aim to offer, I believe that > letting Nautilus do it for us is a far superior idea. The only thing I'm personally interested in is being able to browse and download from the very few FTP sites left on the Internet. Having ephy launch the scheme handler seems like the quickest/easiest way to fix this problem.
All the discussions I had with the designers lead me to believe we in general want to show inline views of the content in the browser when possible (think of the mockups for music, images, etc in the Design page). I think showing the contents of the FTP directory in ephy is the way to go, and going back and forth between nautilus and the browser would be a pain in the ass for most use cases. If anyone wants to do complex operations they can just use nautilus from the get go. That being said, while we don't support this, I think launching the ftp handler in the system makes sense.
We can add an infobar to instruct the user that Nautilus (Files) is available for more complex FTP operations like upload or copying full directories.