<div dir="ltr"><div><span style="font-size:12.8000001907349px">> Quickly scanning the bug I couldn't figure out whether you added hooks</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px">to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px">see the discussion in this bug:</span><br style="font-size:12.8000001907349px"><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px"> </span><a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091" target="_blank" style="font-size:12.8000001907349px">https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091</a><br style="font-size:12.8000001907349px"><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px">My personal opinion is that these schemes should only have an effect</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px">if you navigate to them, not if you fetch them (the latter should</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">> </span><span style="font-size:12.8000001907349px">result in a network error in my opinion).</span><br></div><div><br></div><div>Current implementation doesn't hook to HTML's navigation directly. We delegate the html navigation(or call native application) to application.</div><div>Application is able to decide to navigate the given html page or execute native application through the patch. As far as I know, Chrome also has</div><div>similar implementation.</div><div><br></div><div>If this feature can be landed, I have a plan to test this scenario based on mock implementation.</div><div><br></div><div>Gyuyoung.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 22, 2015 at 5:52 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 1:50 PM, Gyuyoung Kim <<a href="mailto:gyuyoung.kim@webkit.org">gyuyoung.kim@webkit.org</a>> wrote:<br>
> I also don't want to support the "content handler" feature at the moment.<br>
> The feature might be more clear and mature. The patch of Bug 92749 only<br>
> supports registerProtocolHandler,<br>
> and unregisterProtocolHandler and isProtocolHandlerRegistered are supported<br>
> as optional.<br>
><br>
> <a href="https://bugs.webkit.org/show_bug.cgi?id=92749" target="_blank">https://bugs.webkit.org/show_bug.cgi?id=92749</a><br>
<br>
</span>Quickly scanning the bug I couldn't figure out whether you added hooks<br>
to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,<br>
see the discussion in this bug:<br>
<br>
<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091" target="_blank">https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091</a><br>
<br>
My personal opinion is that these schemes should only have an effect<br>
if you navigate to them, not if you fetch them (the latter should<br>
result in a network error in my opinion).<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
<a href="https://annevankesteren.nl/" target="_blank">https://annevankesteren.nl/</a><br>
</font></span></blockquote></div><br></div>