Update: in good old brown paper-bag bug tradition we messed up the soversion calculation in 1.1.2, so please use the new and improved 1.1.3. Sorry for the trouble 🙂
—
As promised, just before GNOME 2.26, two new releases.
First, WebKitGTK+ 1.1.2, now from our brand new website (created by Christian Dywan, kindly hosted by Igalia). It brings two weeks of improvements, this is the NEWS file:
– Added support for downloads: a new signal, ‘download-requested’,
will be emitted by WebKit when a download is requested. On top of
that, the download process has been encapsulated in a new object,
WebKitDownload, which allows the user to control it or to start
new downloads from the client side.
– Added webkit_web_view_get_encoding to get the automatic encoding
of the current page.
– Added GObject properties for ‘encoding’ and ‘custom-encoding’.
– Added ‘javascript-profiling-enabled’ property to the WebInspector,
which allows to enable and disable the profiling functionality.
– Added API to create and add history items to WebKit’s history.
– Improved debugging support with WEBKIT_DEBUG environment
variable. Most of the settings will only give useful output for
debug builds, but WEBKIT_DEBUG=Network will log all HTTP traffic
form libsoup to console. See WebCore/platform/gtk/LoggingGtk.cpp
for all the options available.
– Lots of bugfixes.
Get it in our download page!
One last thing about WebKitGTK+: we plan to release one *unstable* 1.1.x version every two weeks until GNOME 2.28, where we’ll release a new stable 1.2.0 version (basically, we follow GNOME/Kernel versioning system). As in GTK+, the stability of newly introduced API during the development cycle is not guaranteed; we won’t break it willy-nilly, but we’ll do it if we feel we have to in order to get the best possible API.
Second, the first Epiphany release of the WebKit era: Epiphany 2.27.0. This is the first unstable release of the 2.27.x cycle, and the goal is to get as many people as possible testing it to have a solid 2.28.
What’s in it?
We have some new pretty eye candy, like the new progress-in-entry (thanks to the GTK+ guys for the functionality and to Benjamin Berg for the emergency theming fix!):
We suppor the WebKit WebInspector, with similar functionality to the Firefox Firebug extension:
We are also fixing “historical” bugs, like an option to force all windows to be opened in a tab (gconf key /apps/epiphany/general/open_new_windows_in_tab), or storing all auth data in gnome-keyring (already working for HTTP auth if you pass –enable-gnomekeyring to WebKitGTK+, storing auth data from forms is still missing).
We have done a lot since those early snapshots that were shipped with 2.22.x and 2.24.x (until we removed them because people thought that was the state-of-the-art webkit backend, which has always been in trunk and has never been released until now), and the browser is well into ‘dogfoodable’ territory, so I encourage everyone interested to give this a try and report all issues.
Thanks to all the contributors to WebKit and all the other modules we use, it’s a pleasure to be one little cog in the machine 🙂
Thanks for all the work, WebKitGTK+ team!
(posting from Epiphany 2.27.0!)
Awesome. Could I suggest that someone create a package repository (a launchpad PPA, perhaps) to host the bleeding edge Epiphany? It could have nice results with regards to getting people testing it 🙂
It would be great to have a browser seriously ready to compete with Firefox on the GNOME desktop, enough so that distros consider switching. (For the sake of a friendly user experience and all that).
Pingback: Questo piede scotta¹! « pollycoke :)
Pingback: » Questo piede scotta¹!
I second the PPA request.
Thirded! Really looking forward to testing 2.27.
yes a PPA repository would be wonderful.
At the people requesting a PPA: I have prepared some preview (as in, webkit 1.1.1 and Epiphany a week before 2.27.0) packages for Debian unstable/experimental. If anyone is interested in creating an Ubuntu PPA, most of the work is done, and can be found here: http://people.debian.org/~kov/webkit/. Please contact me if you are going to work on such a PPA (kov@debian.org).
I am planning to upload more robust packages of WebKitGTK+ 1.1.2 and Epiphany 2.27.0 to Debian experimental this week, as well.
Firebug is the only reason I still use Firefox. With this new inspector, I’ll be using Epiphany fulltime! Thanks all devs!
Yay! This is really something I have waited for.
Thanks!
Hey,
Great to see progress here 🙂
Is the annoying “problem”, where Epiphany don’t put the cursor right into the navigator-entry after opening a new tab fixed?
I really hope it is, so I can switch to Epiphany 🙂
Pingback: Loren Bandiera’s weblog » Blog Archive » WebKit/Epiphany
@Kris: If you have the home page pointing to Google or something like that then makes sense to go to the search entry on it when you open a new tab (you can still go to the navigator-entry just pressing ctrl+L). You can also define your home page as a blank page so you get the focus of the cursor to the navigator-entry after opening a new tab.
Awesome !
I’ve been waiting for Epiphany to go the WebKit route for a long time, and those are great news.
But just like daniel, Firebug is the only thing that prevented me from using Epiphany full time, as I needed it for we development.
You just made may day 🙂
so awesome! Just can’t wait to have my hand dirty with WebKit, Epiphany rocks too!
I got:
`test -f ‘WebCore/bindings/js/JSCSSValueCustom.cpp’ || echo ‘./’`WebCore/bindings/js/JSCSSValueCustom.cpp
WebCore/bindings/js/JSCSSValueCustom.cpp: In function ‘JSC::JSValuePtr WebCore::toJS(JSC::ExecState*, WebCore::CSSValue*)’:
WebCore/bindings/js/JSCSSValueCustom.cpp:63: error: ‘JSSVGPaint’ was not declared in this scope
WebCore/bindings/js/JSCSSValueCustom.cpp:63: error: no matching function for call to ‘createDOMObjectWrapper(JSC::ExecState*&, WebCore::SVGPaint*)’
make[1]: *** [WebCore/bindings/js/libWebCore_la-JSCSSValueCustom.lo] Errore 1
make[1]: uscita dalla directory «/home/grigio/Sources/webkit-1.1.3»
make: *** [all] Errore 2