<div dir="ltr"><div style="font-size:12.8000001907349px">>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:<a href="https://html.spec.whatwg.org/#custom-handlers" target="_blank">https://html.spec.whatwg.org/#custom-handlers</a></div><div><br></div><div>Yes, the custom-handlers specification only allows us to use specific schemes, and current WebCore implementation was implemented based on the spec.</div><div>Current supported schemes are only below,</div><div><br></div><div><div> "bitcoin", "geo", "im", "irc", "ircs", "magnet", "mailto", "mms", "news", "nntp", "sip", "sms", "smsto", "ssh", "tel", "urn", "webcal", "wtai", "xmpp"</div></div><div><br></div><div><br></div><div><span class="im" style="font-size:12.8000001907349px">>> (I am more dubious of the content handler aspect.)<br><br></span><span style="font-size:12.8000001907349px">>Agreed, especially as it requires the service to download the resource</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">>again. For that use case we need something smarter where you can pass</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">>along an object/stream of sorts I think.</span><br></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">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,</span></div><div><span style="font-size:12.8000001907349px">and unregisterProtocolHandler and isProtocolHandlerRegistered are supported as optional.</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"> </span><a href="https://bugs.webkit.org/show_bug.cgi?id=92749" target="_blank" style="font-size:12.8000001907349px">https://bugs.webkit.org/show_bug.cgi?id=92749</a><span style="font-size:12.8000001907349px"><br></span></div><div><br></div><div>Gyuyoung.</div><div><span style="font-size:12.8000001907349px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 22, 2015 at 12:50 PM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@annevk.nl" target="_blank">annevk@annevk.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, May 22, 2015 at 12:26 PM, Maciej Stachowiak <<a href="mailto:mjs@apple.com">mjs@apple.com</a>> wrote:<br>
> (I am more dubious of the content handler aspect.)<br>
<br>
</span>Agreed, especially as it requires the service to download the resource<br>
again. For that use case we need something smarter where you can pass<br>
along an object/stream of sorts I think.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
<a href="https://annevankesteren.nl/" target="_blank">https://annevankesteren.nl/</a><br>
_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
</div></div></blockquote></div><br></div>