Unify current feed: warning with our nsIContentDispatchChooser

NEW
Unassigned

Status

Camino Graveyard
General
10 years ago
8 years ago

People

(Reporter: Stuart Morgan, Unassigned)

Tracking

Trunk
x86
Mac OS X
Bug Flags:
camino2.0b1 -

Details

(Whiteboard: l10n)

(Reporter)

Description

10 years ago
Spun out of bug 389687; we shouldn't have two different behaviors for feed: links depending on whether they come from chrome or content. I see two options:

1) Special case feed:, so that nsICDC uses the current UI for feed:, and leave everything else the way it is.

2) Make the current feed UI generic, and make that the nsICDC UI, so that the warning will always have a popup for picking a handler (essentially, our own take on FF3's choice box).

I'd be in favor of exploring 2, since I think the popup menu is slim and clean enough that adding it to the warning dialog is a win.
Given the OS's propensity, in absence of an explicit user choice, to pick an app at "random" if you have >1 apps for the protocol installed, 2 sounds like a very good idea.
(Reporter)

Updated

10 years ago
Whiteboard: l10n
Nominating for b2 because of l10n impact, but if Stuart's not working on this, this probably gets kicked from 2.0.
Flags: camino2.0b1?
(Reporter)

Comment 3

10 years ago
Let's push it; we have bigger fish to fry.
Flags: camino2.0b1? → camino2.0b1-
Target Milestone: Camino2.0 → ---
You need to log in before you can comment on or make changes to this bug.