For me, one of the most important problems we face with WebKit is its lack of accessibility support right now. I have a great fear that Alp may have grossly underestimated the scope of the work. I have some confidence, however, that the WebKit folks who were at GNOME Boston should be able to do a decent analysis of what it will take to add it.
I so wish I wrote down all the names of the WebKit folks that were at GNOME Boston. I'd like to follow up to see how their exploration is coming along. Will On Thu, 2008-11-06 at 18:48 +0100, Richard Hult wrote: > Frederic Peters wrote: > > http://mail.gnome.org/archives/devel-announce-list/2008-August/msg00001.html > > > > + WebKit/GTK+ (external dependency): > > - lots of community support > > - accessibility support might not be good enough (no reply from > > WebKit/GTK+ people) > > - epiphany will still use Gecko for 2.24 > > - yelp is still using Gecko at the moment (there's a WebKit branch) > > - devhelp trunk is WebKit-only > > - evolution people intend to use WebKit in 2.26 > > - we'd prefer to avoid depending on both Gecko and WebKit at the same > > time > > => rejected for 2.24, but we'll propose a general switch for 2.26 > > Ah, thanks. I'll keep hacking away in trunk and hope we can ship that > for 2.26 then (and fall back to the old branch again if not). > > /Richard > _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
