[Webkit-unassigned] [Bug 29651] [HTML5] Add a way for an application to register as a protocol handler.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=29651


Peter Kasting <pkasting at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pkasting at google.com




--- Comment #5 from Peter Kasting <pkasting at google.com>  2009-09-24 14:22:54 PDT ---
(In reply to comment #3)
> >It's not clear to me why this is #if'd at all given that the default behavior is to do nothing.
> The API simply passes information to the UA.  This is done by adding the
> runJavaScriptRegisterProtocolHandler pure virtual function to the ChromeClient
> interface defined in WebCore/page/ChromeClient.h.  If it is not defined in the
> codebase of the UA using webkit, compilation will break.  If it is dynamically
> linked, then a runtime failure will occur.  As with the introduction of
> Workers, perhaps it is better to leave it behind the ENABLE_ flag for a while?

In the past I believe minor things like this have been added by simply adding
stubs to the ports whose implementations are available in the WebKit tree.  I
think that would be fine for this, I see no need to add an ENABLE_ flag.

OTOH, I would very much like to see registerContentHandler supported here too. 
Why add one and not the other?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.