Runner for jasmine 2

The old script needed some updates in order to support the new jasmine lib
Adding "test/ghostdriver-test" to run in Travis CI

Related to issue #11880
Making GhostDriver test "quiet-er" (and parallel)

Also, trying to get the exit status of those tests reported, in case they fail.

Related to #11952.
Run PhantomJS's tests as part of TravisCI

Related to #11952.
Fixed tests that dealt with manipulating request URLs.

Related to #11952.

Those tests use "http://phantomjs.org" as fixture.
The website "/images" directory has been renamed "/img",
breaking the tests.

Maybe not the greatest way to go about it, but
for now it will do. We probably need to have fixtures
served by a local server.
Changing Travis CI build list into a table
Update example

Since this example was written the phantomjs home page has been redesigned and the targeted ID no longer exists. This tweaks the example so that it can again find content to report.
Merge branch 'master' of https://github.com/pauloalem/phantomjs into pauloalem-master
Fix harfbuzz assertions using patch from Chromium.

Exotic text (e.g. attempting to render a binary file such as .zip
or .exe as a webpage) can trigger an assertion failure in the
Harfbuzz code. Chromium developers also noticed this issue and
committed a patch to fix it:

http://lists.freedesktop.org/archives/harfbuzz/2009-August/000354.html

This patch has not been accepted by upstream, but this (old) version
of Harfbuzz has been abandoned and superceded by Harfbuzz-NG.

Issue #11264
Use SVG version of travis build status badges

https://github.com/ariya/phantomjs/issues/11880
Added setProxy function

https://github.com/ariya/phantomjs/issues/10803
Example of runtime proxy setup

https://github.com/ariya/phantomjs/issues/10803
Add missing RPM spec file names; update changelog.

Issue #11262 https://github.com/ariya/phantomjs/issues/11262
Adding IRC #phantomjs notif. to TravisCI build
Don't scale the unit px to 1/2.54 points for PDFs

The unit px is one point inside the HTML source page but phantomjs handles it
without reason as 1/2.54 points. This makes the page smaller than expected when
trying to render a page as PDF.

https://github.com/ariya/phantomjs/issues/11590 ("page.paperSize is not
accurate for .pdf")
Disable page shrinking for pdf printing to create accurate output

PDFs are not rendered like PNG or other image formats by phantomjs because it
uses the printer functionality of Qt+Webkit. But Webkit uses some printer
"optimization" to save paper by shrinking the output. Such shrinking results in
too small content on a page.

https://github.com/ariya/phantomjs/issues/11590 ("page.paperSize is not
accurate for .pdf")
Use correctly rendered pdf for webpage-spec-renders tests

The last reference test.pdf in the tests was using a complete different region
of the input "image.jpg" because the used phantomjs version used to generate it
had a bug. This bug was fixed in 833eb824f5bae07f1b157d6757e7e3c98343f812
("Don't scale the unit px to 1/2.54 points for PDFs") and
1daa2eb4dd49efb848ff96e37f298a774520cc9b ("Disable page shrinking for pdf
printing to create accurate output").

The new version should now use the same region of the input image as the other
generated files for the gif, jpg and png tests. The only difference is the
extra height is still displayed on a second page but this is currently expected
by phantomjs.

https://github.com/ariya/phantomjs/issues/11590 ("page.paperSize is not
accurate for .pdf")
Expose HTTP status and reason to onResourceError (#12252).
Replace proxy initialization with existing method

Since we have setProxy() method, we can replace the existing code
block in Phantom::init() with simple method call getting rid of
duplicated code.
Merge pull request #12300 from artkoshelev/proxysetuprefactoring

Replace proxy initialization with existing method