~abreu-alexandre/oxide/add-ua-to-downloadrequested : changes

~abreu-alexandre/oxide/add-ua-to-downloadrequested » Changes from revision 1104

From Revision 721 to 702

Rev	Summary	Authors	Tags	Date
721	Give each test its own datadir. Should hopefully fix LP: #12... Give each test its own datadir. Should hopefully fix LP: #1278315	Chris Coulson		9 years ago
720	Tidy up the cmake files a bit. The include files are gone - ... Tidy up the cmake files a bit. The include files are gone - they aren't needed anyway and it wasn't really obvious where new variables should go. The changes also fix a problem where running cmake in a cross-compile set up with a cache file already seems to fail	Chris Coulson		9 years ago
719	Split the event loop implementation in runtests.py in to its... Split the event loop implementation in runtests.py in to its own module	Chris Coulson		9 years ago
718	Bump Chromium rev to 39.0.2145.4 Bump Chromium rev to 39.0.2145.4	Chris Coulson		9 years ago
717	Add @run-at document-start to TestUtilsSlave.js to hopefully... Add @run-at document-start to TestUtilsSlave.js to hopefully fix some random test failures that look like a race	Chris Coulson		9 years ago
716	Get rid of run-qmltests.cmake - just use run_qmlapp.sh for t... Get rid of run-qmltests.cmake - just use run_qmlapp.sh for this instead	Chris Coulson		9 years ago
715	Add CookieManager.deleteAllCookies and use this in place of ... Add CookieManager.deleteAllCookies and use this in place of clear-test-cookies-hack.py	Chris Coulson		9 years ago
714	Don't initialize NSS with a user DB Don't initialize NSS with a user DB	Chris Coulson		9 years ago
713	Clear the temporary mixed content blocker settings for navig... Clear the temporary mixed content blocker settings for navigations that aren't within the same page (ie, where more than the URL fragment changes) and aren't due to a content-initiated reload. The last one is needed to avoid ending up in an infinite loop	Chris Coulson		9 years ago
712	Add back support for ms since epoch for the expirationdate, ... Add back support for ms since epoch for the expirationdate, as well as ISO8601 strings	Chris Coulson		9 years ago
711	Some minor tweaks to the CookieManager API: Some minor tweaks to the CookieManager API: - Bring back setNetworkCookies as this is being used from C++ code in webbrowser-app. Note that the url parameter is no longer a QString though (it's a QUrl) - Remove the status parameter entirely from the response to setCookies/setNetworkCookies - the problem with this is that it provides no way to know which cookies failed and which ones were set successfully. Instead, replace it by a new parameter (failedCookies) which returns a list of cookies that failed to set. - Having setCookies + cookiesSet and getCookies + gotCookies is a bit confusing. These are now changed to setCookies + setCookiesResponse and getCookies + getCookiesResponse.	Chris Coulson		9 years ago
710	Bump Chromium rev to 39.0.2138.3 Bump Chromium rev to 39.0.2138.3	Chris Coulson		9 years ago
709	Bump qt version to 1.3 Bump qt version to 1.3	Chris Coulson		9 years ago
708	Set the gettext domain to oxide-qt rather than oxide Set the gettext domain to oxide-qt rather than oxide	Chris Coulson	BRANCH_1_2	9 years ago
707	Fix various issues with the CookieManager code: Fix various issues with the CookieManager code: - getNextRequestId() always returns zero - getNextRequestId() depends on undefined beahviour (signed integer overflow) - CookieMonster calls the callbacks synchronously if nothing needs to be loaded from permanent storage. This means that the behaviour of setting one cookie and waiting for the callback to run before setting the next causes the stack to grow depending on the amount of cookies being set (and also means lots of reentry). Rework it to prevent this behaviour. - Ensure that the responses at the API level always do happen asynchronously. - Setting a session cookie always fails because the undefined expiry date gets interpreted as a date far in the past, so Chromium considers the cookie expired. - Ensure that session cookies returned from the API don't have an expiry date way in the past. There are a few minor changes to the API too: - CookieManager.gotCookies does not return a status code now. The only possible errors when reading cookies occur synchronously (ie, the CookieStore is unavailable), so the API just returns an invalid request ID now. - The addition of CookieManager.getCookies(), which allows you to retrieve all cookies for a URL. - The expirationdate attribute now works with the built-in Date type rather than having to give it the expiry in milliseconds since the epoch. The tests have been improved as well to actually test the various cases rather than just calling in to the API and making sure we get a response back	Chris Coulson		9 years ago
706	Add WebView.securityStatus, WebView.blockedContent, Add WebView.securityStatus, WebView.blockedContent, WebView.setCanTemporarilyDisplayInsecureContent, WebView.setCanTemporarilyRunInsecureContent, SecurityStatus, CertificateError and SslCertificate API's. I'm still working on tests for these API's, but this shouldn't block webbrowser-app work	Chris Coulson		9 years ago
705	Bump Chromium rev to 38.0.2125.24 Bump Chromium rev to 38.0.2125.24	Chris Coulson		9 years ago
704	Bump depot_tools to 8f93f79bcee79072a70cf9c8c392ad140f0cecf1 Bump depot_tools to 8f93f79bcee79072a70cf9c8c392ad140f0cecf1	Chris Coulson		9 years ago
703	Make sure we fetch branch heads Make sure we fetch branch heads	Chris Coulson		9 years ago
702	Update for the Chromium GIT migration Update for the Chromium GIT migration	Chris Coulson		9 years ago