[webkit-dev] Drop EFL WK1 port

Maciej Stachowiak mjs at apple.com
Thu Jun 19 11:24:17 PDT 2014

> On Jun 19, 2014, at 7:07 AM, Darin Adler <darin at apple.com> wrote:
> On Jun 19, 2014, at 5:27 AM, pulkomandy <pulkomandy at gmail.com> wrote:
>> Should existing WebKit ports that are WK1 based consider switching to WK2?
> Yes.
> WK1 will be around for the foreseeable future because, on both Mac and iOS, it’s part of the public API that developers can use for apps on those platforms. But on any platform that does not have that kind of legacy restriction, I think it’s a good idea to make the switch to WK2.

We’ve also (finally) announced public API for Mac OS X and iOS that uses WebKit2, the WKWebView (also known as Modern WebKit API). Given this, it’s possible that someday we’ll be able to deprecate WebKit1, but there is a lot of third-party and first-party code using it, so if it ever happens, it won’t be for a long time.

For ports without these legacy constraints, I wouldn’t recommend supporting a WebKit1-based API.


More information about the webkit-dev mailing list