Open Bug 402258 Opened 14 years ago Updated 6 years ago

web-based proto handler "already been added" UI could use some refinements

Categories

(Firefox :: File Handling, defect, P4)

defect

Tracking

()

People

(Reporter: dmosedale, Unassigned)

Details

(Whiteboard: [proto])

Attachments

(1 file)

It may want the hostname with URI on mouseover.

It probably wants a link to the application prefs dialog.

It might also want to behave differently depending on how registerProtocolHandler was invoked: if it was just done while loading the page (see nsPIDOMWindow::IsLoadingOrRunningTimeone), then we probably wouldn't want to show it.  If it's done from an explicit action, we probably would want to show it.
An alternative to this modal behavior might be a way for websites to test if their handler is already registered.

Requesting blokcing-1.9? as this might deserve a wanted-1.9+.
Flags: blocking1.9?
Whiteboard: [proto]
Can you post a screen shot of the UI you are talking about, and describe how it is invoked.
IMO, if you have both Google Mail and Yahoo Mail protocol handlers installed, with Yahoo as the don't-ask-me default, and you go to Google Mail's "register protocol handler" page, you should be able to at least make Yahoo no longer be the don't-ask-me default.
Attached image current UI in question
If a page calls registerProtocolHandler(), and the handler is already registered, the attached notification bar shows up.  If we do end up keeping this bar all the time (i.e. not switching to modal behavior depending when registerProtocolHandler was called), we might also want some UI to allow the user to say "never ask me again".
Priority: -- → P3
Priority: P3 → P4
Flags: blocking1.9? → blocking1.9-
I liked dmose's idea of using the same code that we have for pop-up blocking for detecting if the user clicked a button or link that resulted in calling registerProtocolHandler, as opposed to the page just calling it out of the blue (related to this bug in that there would be less instances of the user being notified about a protocol handler that they have already added).
Product: Core → Firefox
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.