>On the face of it, the registerProtocolHandler API seems more general than
necessary, but the actual spec for it has a whitelist of specific schemes,
most of which seem reasonable for this kind of >purpose:
https://html.spec.whatwg.org/#custom-handlers

Yes, the custom-handlers specification only allows us to use specific
schemes, and current WebCore implementation was implemented based on the
spec.
Current supported schemes are only below,

        "bitcoin", "geo", "im", "irc", "ircs", "magnet", "mailto", "mms",
"news", "nntp", "sip", "sms", "smsto", "ssh", "tel", "urn", "webcal",
"wtai", "xmpp"


>> (I am more dubious of the content handler aspect.)

>Agreed, especially as it requires the service to download the resource
>again. For that use case we need something smarter where you can pass
>along an object/stream of sorts I think.

I also don't want to support the "content handler" feature at the moment.
The feature might be more clear and mature. The patch of Bug 92749 only
supports registerProtocolHandler,
and unregisterProtocolHandler and isProtocolHandlerRegistered are supported
as optional.

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

Gyuyoung.


On Fri, May 22, 2015 at 12:50 PM, Anne van Kesteren <ann...@annevk.nl>
wrote:

> On Fri, May 22, 2015 at 12:26 PM, Maciej Stachowiak <m...@apple.com> wrote:
> > (I am more dubious of the content handler aspect.)
>
> Agreed, especially as it requires the service to download the resource
> again. For that use case we need something smarter where you can pass
> along an object/stream of sorts I think.
>
>
> --
> https://annevankesteren.nl/
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to