* Bugfix release for arch linux compile issues
* Fixes compile errors on arch Linux
Capybara::TimeoutError has been removed.
Required for Capybara::SpecHelper.configure.
From RFC4627: Numeric values that cannot be represented as sequences of digits (such as Infinity and NaN) are not permitted. NaN is invalid, so we already return null.
JSON supports UTF-16, however the serializer is 8-bit clean. Instead of returning a QString only to turn it back into a QByteArray, return a QByteArray on serialization.
WebPage::setUserStylesheet prevents Web Fonts from loading when styles are applied directly to elements, however if the styles are applied to pseudo elements, the override does not apply. This leads to crashes on Mac OS X, likely due to https://bugs.webkit.org/show_bug.cgi?id=61031.
TimeoutCommand may receive pageFinished multiple times before PageLoadingCommand has finished.
If the incorrect credentials are provided QNetworkAccessManager just keeps firing the same signal and it gets stuck in a infinite loop. This change only sets the user name and password if they are different to the current user name and password, causing the event to not be continuously triggered after failed authentications.
Turns Response into a QObject and sets parent to the command that emits it. Each Command is also a child of the decorator commands, Timeout and PageLoading commnds, so that deleting the top level command will delete all the children. See discussion in #430.
WebPage::setContent will cause the loadFinished signal to fire, so there's no need to call loadFinished if the signal is connected.
Instead of emitting loadStarted when a reply is created and pageFinished when all pending replies have finished, emit these signals when the corresponding WebPage events fire.
Synchronous requests will have emitted the finished signal by the time we connect to it.
Workaround for Capybara integration specs which fail to do the same.
The Capybara spec_helper already resets the browser after each spec, so we only need to reset after using the driver via AppRunner.