WebKitGTK+ 1.1.90 is out!

We’re coming close to GNOME 2.30 release date, and we are getting ready to branch a stable release off of WebKit’s svn trunk in preparation for that. The idea of the stable branch is to try to maintain, and improve stability, with no additional features going in. Speaking of features, though, if you’ve been paying attention you will have noticed WebKitGTK+ has come a long way, now.

We came from not having basic features such as download support or openning links in new tabs, a more-or-less working HTML5 media implementation, and very few or missing in action developers to a thriving project, that gets more, and more attention, and contributors every day, with advanced features available, and rocking HTML5 media support that leaves little to be desired. It’s been just over one year since we started rolling mostly bi-weekly releases, each adding more awesome features.

There are still many issues, and we are not always equipped as a team to handle all the specifics of the engine ourselves, but I am really happy with the progress we’ve made, and really thankful for the support my employer Collabora has given all the way for this to happen, including the early work on plugins, and many other things before my time as a contributor. When I switched to using Epiphany with the WebKit backend as my default browser back in January 2009, that meant having to deal with a whole lot of misbehaviour, and work-around a lot of painful brokeness. These days I enjoy a snappy, functional browser that makes me happy.

If you haven’t done so yet, go download, and test the newest Epiphany, with the latest WebKitGTK+, and help us make the GNOME 2.30’s web browser rock even more!

3 thoughts on “WebKitGTK+ 1.1.90 is out!”

  1. There’s still work to do. There’s huge performance issues with the CSS property box-shadow. Go to identi.ca or boagworld.com and try to scroll. Your CPU load is skyrocketing. Very very annoying.

  2. Oh, I didn’t mean to imply there isn’t work to be done. Funny that you mention this specifically, because it’s the exact topic of our conversation right now in #webkit-gtk =). Like I said, it’s a lot of work, and there are so many specificities, and we’re not always knowledgeable or have enough people to tackle everything, but improvements on that are certainly to show up in the near to medium term, as this has been bothering us quite a bit now that bigger bothers are no longer there.

  3. Coincedence you’re talking about it now in the channel. I just wanted to let you know about this specific issue because it’s bothering quite a few people who are using Epiphany now. They sure will be happy when it’ll be fixed. But glad to hear you’re working on it. Keep up the good work.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>