[webkit-gtk] Deciding the deprecation path for WebKit1

Niranjan Rao nhrdls at gmail.com
Wed Mar 19 12:12:56 PDT 2014

One concern I have is webkit 2 does not have complete feature list of 
webkit1 yet. For example in version 2, we can not access WebKitWebFrame 
object.  We were using it, but managed to find workarounds. I don't know 
how many other applications actually use it.

Personally we have moved webkit2. It is little more cumbersome to use 
than older version and added some interesting complications to life. 
However in general, I am noticing it more faster and having more useful 
features. When compared with previous version, we have also noticed 
higher number of crashes in v2, but they will stabilize/get fixed over 
the time.

Gtk annotations is also important for others so that languages like 
python can use it. But this raises a very interesting problem. If python 
like language needs DOM access, how do we do it? There are lot of tools 
out there that depend upon DOM access and use Gtk annotations.



On 03/19/2014 11:46 AM, Martin Robinson wrote:
> On Wed, Mar 19, 2014 at 11:34 AM, Carlos Garcia Campos
> <cgarcia at igalia.com> wrote:
>> Let's remove the code then. As I said people wanting to stay with
>> WebKit1 can use the latest release including WebKit1.
> It seems like a lot of people are in favor of removing the code now.
> We will continue to support WebKit1 for as long as we release the 2.4
> branch (that may be 6 months or even a year). I think this is
> suitable, as it will still be possible to use WebKi1 for some time. If
> someone wants to continue maintaining WebKit1, they can submit patches
> against the 2.4 branch. Is anyone opposed to this?
> --Martin
> _______________________________________________
> webkit-gtk mailing list
> webkit-gtk at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-gtk

More information about the webkit-gtk mailing list