Closed Bug 234714 Opened 21 years ago Closed 9 years ago

provide a mechanism to support drop-in unknown protocol handlers

Categories

(Core :: Networking, enhancement)

Product:
Core
Component:
Networking
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla39

People

(Reporter: darin.moz, Unassigned)

Details

(Keywords: arch) 

provide a mechanism to support drop-in unknown protocol handlers.  this stems
from the work done for bug 233305 (to add gnome-vfs support).  the patch for
that bug needed to intercept handling of an unknown protocol to check if it can
be satisfied using gnome-vfs.  a category manager based solution might be
better, or perhaps we'd want something that allowed us to stack the handlers in
some kind of prioritized order... with the "default" protocol handler being
given the lowest priority (or something like that).
Severity: normal → enhancement
Status: NEW → ASSIGNED
OS: Linux → All
Hardware: PC → All
Target Milestone: --- → mozilla1.8alpha
Keywords: arch
Target Milestone: mozilla1.8alpha1 → Future
Assignee: darin → nobody
Status: ASSIGNED → NEW
QA Contact: benc → networking
Target Milestone: Future → ---
Is this feature still needed now that we are dropping GnomeVFS support in favor of GIO? GIO implements the Freedesktop standards for searching .desktop files to find default protocol handlers.

In particular, I'm looking at https://hg.mozilla.org/mozilla-central/file/67b9d5593e2c/netwerk/base/nsIOService.cpp#l469 and wondering if the comment there can be deleted along with the surrounding GnomeVFS code.
Flags: needinfo?(darin.moz)
See bug 1134537
I'm calling this fixed as of https://hg.mozilla.org/mozilla-central/rev/bc720b50b4e9

See https://bugzilla.mozilla.org/show_bug.cgi?id=1134537#c26
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(darin.moz)
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
You need to log in before you can comment on or make changes to this bug.