It seem to me there are both agreements and objections to support this feature in WebKit2. It looks many web contents have already used some custom schemes as 'mailto://', and In my humble opinion, the feature will be able to improve the usage of the custom scheme. Besides we can control the supported custom schemes because the feature only supports pre-defined custom schemes. Web content is only able to use the pre-defined custom schemes. In my opinion, it would be good if the feature is supported by WebKit2 although it is added as an experimental feature using #ifdef.
However If WK2 owners still think this feature needs to be more stable, I will wait until they agree it. Gyuyoung. On Sat, May 23, 2015 at 12:36 PM, Gyuyoung Kim <gyuyoung....@webkit.org> wrote: > 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 good if we add a test to check it. Let me do it. > > Gyuyoung. > > On Sat, May 23, 2015 at 9:55 AM, Anne van Kesteren <ann...@annevk.nl> > wrote: > >> 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 >> > native application through the patch. As far as I know, Chrome also has >> > similar implementation. >> >> Okay, so >> >> <img src=mailto:...> >> >> results in a network error and not a fetch to the registered URL? >> >> >> -- >> https://annevankesteren.nl/ >> > >
_______________________________________________ webkit-dev mailing list email@example.com https://lists.webkit.org/mailman/listinfo/webkit-dev