[webkit-dev] Does any port implements Navigator.registerProtocolHandler and Navigator.registerContentHandler?

David Levin levin at chromium.org
Wed Jul 7 19:55:03 PDT 2010

On Wed, Jul 7, 2010 at 5:24 PM, Peter Kasting <pkasting at google.com> wrote:

> On Wed, Jul 7, 2010 at 5:00 PM, Dmitry Titov <dimich at chromium.org> wrote:
>> I'd lean to the removal, unless there is a port that has work ongoing or
>> planned soon for those implementations.
>> Does anybody vote for #ifdefs?
> I vote against removal if only because Chromium has really wanted these
> badly for a long time and simply hasn't been able to find someone to
> implement them.  Perhaps I could make it worth your while to implement
> rather than remove the stubs?  :)

*Even if someone to implement them for chromium, it doesn't seem to fix the
overall problem. *Dmitry indicated that the presences of these is breaking
feature detection in browsers using WebKit (-- which is something being
heard from web developers).

A simple solution is to remove them. Later, any port (including chromium)
who gets someone to work on them could re-add these methods back properly
under ifdef's.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20100707/6e1b0a78/attachment.html>

More information about the webkit-dev mailing list