Re: [webkit-dev] Support registerProtocolHandler in WebKit2

2015-05-22 Thread Anne van Kesteren
On Fri, May 22, 2015 at 1:50 PM, Gyuyoung Kim gyuyoung@webkit.org wrote: 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

Re: [webkit-dev] Support registerProtocolHandler in WebKit2

2015-05-22 Thread Anne van Kesteren
On Fri, May 22, 2015 at 6:43 PM, Gyuyoung Kim gyuyoung@webkit.org wrote: Current implementation doesn't hook to HTML's navigation directly. We delegate the html navigation(or call native application) to application. Application is able to decide to navigate the given html page or execute

Re: [webkit-dev] Support registerProtocolHandler in WebKit2

2015-05-22 Thread Gyuyoung Kim
Hi Anne, I need to verify the behaviour using the patch though, I think the registered URL isn't fetched under current patch of Bug 92749. However I need to check if the registered URL is passed to application under the patch's implementation. If this feature will be landed to WK2, it would be

Re: [webkit-dev] Support registerProtocolHandler in WebKit2

2015-05-22 Thread Gyuyoung Kim
Quickly scanning the bug I couldn't figure out whether you added hooks to HTML's navigate algorithm or Fetch' fetch algorithm. In particular, see the discussion in this bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091 My personal opinion is that these schemes should only have an

Re: [webkit-dev] Support registerProtocolHandler in WebKit2

2015-05-22 Thread Gyuyoung Kim
Quickly scanning the bug I couldn't figure out whether you added hooks to HTML's navigate algorithm or Fetch' fetch algorithm. In particular, see the discussion in this bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091 My personal opinion is that these schemes should only have an