Closed Bug 258799 Opened 20 years ago Closed 9 years ago

Need UI to manage external protocol handlers

Categories

(Core :: Networking, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dveditz, Unassigned)

Details

(Whiteboard: [l10n impact unknown])

Need a pref to manage external protocols, so that if a user allows or blocks a particular one they can later change their mind without having to know about or use about:config Possibly should also surface the pref setting for the default behavior (don't load, always load, ask). With the patch for bug 173010 "ask" is the initial setting.
Summary: Need UI to manage external protocols → Need UI to manage external protocol handlers
From Bug 173010 comment #23 (Darin Fisher (IBM) said): I think that UI for this security feature should be a requirement for Firefox 1.0. We should probably leverage the "banner"-based UI notification, and provide a management interface similar to what is currently provided for other things like XPI whitelisting. Only, this would apply to URL schemes instead of hostnames.
Flags: blocking-aviary1.0?
Do we need to get UI additions/changes in before PR?
Flags: blocking-aviary1.0PR?
Not going to happen before PR.
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0+
Should this go into the file types list? That's how Windows handles it.
Does this have l10n impact? If so, you have about 24 hours to land the strings.
Whiteboard: [l10n impact unknown]
Not a "blocker"
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
Severity: normal → enhancement
QA Contact: benc → networking
Assignee: dveditz → nobody
if this is an urgent need, feel free to reopen.. probly as a front end bug tho
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.