[whatwg] Proposal to extend registerProtocolHandler

Olli Pettay Olli.Pettay at helsinki.fi
Wed Jul 6 11:41:01 PDT 2011

On 07/06/2011 07:51 AM, Robert O'Callahan wrote:
> I don't think browsers need to prompt for registerProtocolHandler. Instead,
> I would simply allow any site to register as a protocol handler for almost
> anything, and remember all such registration

So all the ad sites (which are embedded via iframe or something) would
just register all the possible protocols so that some user might
accidentally use their site for protocol handling - especially if the 
site was the first one to register the protocol.
Doesn't sound too good.


>  When the user navigates to a
> URI whose protocol has had an app newly registered for it since the last
> such navigation, then prompt the user to choose which app to use. The UI for
> that prompt would give prominence to the previously-seected app (if any),
> followed by any newly registered app(s), and would remember the choice. The
> UI could be modal or non-modal.
> It seems to me that this approach would address the issues James Kozianski
> raised in part 1 of his email, obviating the need for an isRegistered()
> function.
> Rob

More information about the whatwg mailing list