It appears they've moved forward to Qt5 but they're still running on QtWebKit. This is a bad situation since QtWebKit has been deprecated (read: nobody has publicly committed to writing any new code for it, not least Digia) in favour of QtWebEngine, which doesn't have even 10% of the API richness of the old module.
WebEngine implements process separation and is based on Blink, whereas WebKit was in-process and e.g. allowed direct access to DOM from C++.
The job of moving PJS to WebEngine, if possible, when it happens will basically be the same effort as a rewrite. This release looks like a stopgap to get the best of the old WebKit line, but calling it 2.0 seems a bit shortsighted -- 2.0 should be kept for the WebEngine series if/when it happens.
The most important thing we wanted to achieve was to get a fresh version of QtWebkit. Which was not possible without upgrading to Qt5. We had plans to switch to QtWebEngine in future versions. But in current state, we're thinking about moving to Chromium.
Only on Linux and OS X. Windows version doesn't support WebFonts yet. We will enable them in the next minor release (2.0.1). It will be available shortly.
I'd really like PhantomJS to declare issue bankruptcy on their Github repo, which is currently a whopping 1,367 issues, many of which are just pastes of core dumps with no replies.
Wiping the slate clean with Phantom 2, combined with any changes that enable more contributors to fight down the issues list, could lead to PhantomJS being a much more solid project.
New features
* Switched to Qt 5 and updated WebKit (issue 10448)
* Implemented clearing of memory cache (issue 10357)
* Added support for HTTP header change for every request (issue 11299)
Improvements
* Fixed rendering of CJK text by always linking the codecs (issue 10249)
* Ensured onResourceReceived is still fired on an error (issue 11163)
* Fixed possible crash in handling network requests (issue 11252)
* Removed hardcoded GhostDriver launching message (issue 12681)
* Allowed disk cache more than 2 GB (issue 12303)
Examples
* Netsniff example should exit when fails to load (issue 11333)
"A: If you want to know HTML5/CSS3/other features supported by PhantomJS, using WebKit version is not a good idea. See Supported Web Standards documentation page for details.
If you really like to get the WebKit version, find it via the user agent, run the examples/useragent.js. The actual version depends on the libraries with which PhantomJS was compiled."
I can't understand this. Why is it bad to know that they use webkit X? When I was struggling with previous versions of PJS the soulition was to realize what I wanted wasn't supported in that version so I needed a workaround.
Kind of. Before we will do official announcement we have to complete following things:
- compile binaries for Linux X86/X64
- update links/information blocks on our web site.
Thank you for the hard work on this major version release. I use it in a side project and PhantomJS2 has greatly improved it's performance among other things.
edit: http://phantomjs.org/release-2.0.html has more meaningful information