Closed Bug 297645 Opened 14 years ago Closed 7 years ago
handle ed2k links
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2) "ed2k" is a wrapper for ed2k links provided by most (all?) edonkey2000 protocol implementations. --- mozilla-firefox-1.0.4.old/browser/app/profile/firefox.js 2005-06-14 14:20:41.000000000 +0200 +++ mozilla-firefox-1.0.4/browser/app/profile/firefox.js 2005-06-14 14:27:06.000000000 +0200 @@ -309,6 +309,11 @@ pref("network.protocol-handler.expose.snews", false); pref("network.protocol-handler.expose.nntp", false); +// "ed2k" is a wrapper for ed2k links provided by most (all?) edonkey2000 +// protocol implementations +pref("network.protocol-handler.app.ed2k", "ed2k"); +pref("network.protocol-handler.warn-external.ed2k", false); + // Default security warning dialogs to show once. pref("security.warn_entering_secure.show_once", true); pref("security.warn_entering_weak.show_once", true); Reproducible: Always
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Confirming feature request.
Status: UNCONFIRMED → NEW
Component: OS Integration → Preferences
Ever confirmed: true
OS: Linux → All
QA Contact: os.integration → preferences
Hardware: PC → All
Any news on this?
The above posted fix is so simple and benevolent! it should be made a part of Firefox 3, since it can't harm the Fx3 in any way. I hereby request blocking‑firefox3 or wanted‑firefox3 from drivers.
Also noticed that support is missing for lasfm://, itsp://, peercast://, etc. Looks like everyone likes to come up with their own URL scheme. Thinking about it (and considering how long it takes to get oneself heard ;-)), maybe it's better if we solve all in one run. There's already a program that can handle them all: xdg-open, so why not offload the effort into it, sharing it with other browsers and whatnot? I propose: pref("network.protocol-handler.app.default", "xdg-open");
Erm sorry, there's no such thing as "network.protocol-handler.app.default". I got confused with gconf schemas. Which sounds like a solution can be provided this way (e.g. by shipping a schemas file in amule et al). I'll investigate.
Mike Hommey confirmed this to me in Debian BTS. I'll pursue that for handling ed2k links. Though, it doesn't harm to fix it in Firefox as well, of course.
Way too late to add new handlers or handler code, trying to lock down for ship. Maybe next cycle, if a well reviewed and safe patch is available.
Flags: blocking-firefox3? → blocking-firefox3-
Not enough demand for this, and as far as I know this should already work if there is a properly registered system handler for this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.