W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2006

[whatwg] Registering protocol handlers

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 27 Apr 2006 00:49:59 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0604262032560.21459@dhalsim.dreamhost.com>
On Tue, 25 Apr 2006, Christian Biesinger wrote:
> > 
> > The spec is just there to make sure that if the page _does_ use the 
> > feature, it can do so in a way that will lead to predictable _server 
> > side_ results, independent of the user agent used.
> 
> OK. I still think that pages would like to know for what content exactly 
> their registered handler will be used ...

That isn't really how the Web works...


> > I'm not sure what you're saying here. The API is just a way to say "I 
> > can handle this type", it's not a way of saying "I want to handle all 
> > content of this type". Is the spec misleading about this? Let me know 
> > if I can reword something to reduce the confusion here.
> 
> I think it is. Consider this sentence:
> "Analogously, the registerContentHandler()  method allows Web sites to
> register themselves as handlers for content in a particular MIME type."
> 
> To me that sounds like "wants to handle (all) content of that type". I 
> suppose the next sentence is trying to clarify this. But if that's not 
> the meaning, I think the sentence should be clarified, although I can't 
> think of a good wording at the moment.

Ok, changed it to "register themselves as possible handlers". Is that 
better?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 26 April 2006 17:49:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:46 UTC