Hi Ian, Here are the use cases I had in mind:
1. Allow sites to conditionally show UI to promote the advantages of registering the site as a handler. (requires isRegistered) 2. Allow sites to provide settings screens which allow users to register / deregister handlers from within the site. (requires isRegistered, and deregisterProtocolHandler) The presence of an ignored list - sites who don't have permission to use registerProtocolHandler - necessitates Michael Davidson's suggestion that isRegistered() should return a tri-state value (REGISTERED, DECLINED, NOTASKED). Otherwise sites that have been 'ignored' by a user won't be able to tell if they should show their promotional UI or not. Cheers, James On Sat, Jul 23, 2011 at 8:33 AM, Ian Hickson <[email protected]> wrote: > On Thu, 21 Apr 2011, James Kozianski wrote: > > > > I'd like to propose the following changes to the registerProtocolHandler > > spec. [...] > > Before I study the proposals in detail, is there a description of the > kind of experience we're trying to enable here? > > What are the UIs we expect to see page use wih registerProtocolHandler()? > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' >
