We are mapping a single QTouchEvent to
multiple MotionEventQt for Chromium.
For gesture recognition it is important
that these motion events are being processed
in a sorted manner, as a move event might
trigger a different gesture depending on
how many ACTION_DOWN or ACTION_POINTER_DOWN
were received before.

It is particularly illegal to process an ACTION_MOVE
with multiple touch points without having received
a ACTION_POINTER_DOWN before.

Change-Id: I75d22dd845774a14b5f590e0e0ce46263c4a49f4
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Callers inside Chromium expect an implementation of AccessTokenStore to exist.
This fixes crashes with the geolocation-based APIs, exposed on e.g. google.com
when faking an Android UA (as well as other places, probably).

Change-Id: I45e6b483e096d5165fefd86927cdf34e799cc4d9
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Change-Id: I3b7df1ada08a8985734d804208b50cd5e0403903

ANGLE isn't thread-safe and we're already taking a risk by letting
Chromium do texture upload from the GPU thread with a shared GL
context.

Any kind of drawing happening concurrently between the GPU thread and
the Qt scene graph thread might currently end up drawing on the same
device context and this is creating visual artifacts and Direct3D
errors.

We're already disabling WebGL but we should also disable accelerated
2D canvas rendering to lower that risk. We should ultimately disable
ANGLE from within Chromium or fix multithreading issues to properly
support GL rendering scenarios across threads.

Task-number: QTBUG-41627
Change-Id: I37a7a778f0e1066a454f51bb38e98df4dea8767e
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>

Change-Id: I2d04e910c7a08e1c630bc490d1f8b1be3d27a6f1
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Change-Id: I7cb497ce0f67eaf948caa88930fa1a3040ff4c39
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I01615a492c958bf123deeef5d2ddf9fb01b1a9d0

We should save our cache in the configured CacheLocation, and ensure
we are prepared for multiple BrowserContext by caching to a Default
subdir. This matches how chromium caches on linux.

Change-Id: Ibe914fca35435ea1658565be87747cfabc71e97b
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

The feature enum names and documentation gave the impression it could
control audio and video output, while they only control input.

Also removed documentation of non connected feature permissions for
Notifications and GeoLocation.

Change-Id: Ia35142ca691ebd6059b7472e9803fda8cbd84813
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Error page should be disabled while testing loadFail signal since
testing signals of the internal error page is not possible yet.

Change-Id: I07f0bb6378fcbf5d18634197808801c94606803c
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Remove QQuickWebEngineSettingsPrivate object's pointer from the global
setting list before the object is destructed.

Change-Id: I1cca6bf8aa2438903692d9e2ef863c8fc543adbd
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

There is currently no convenient way to deploy QtWebEngine into an application
bundle on OSX. macdeployqt copies frameworks into a .app bundle's Frameworks
directory but this makes no sense unless all the needed files are also
distributed with the bundle.

This patch moves:
- The ffmpegsumo.so library into Libraries/
- Locale .pak files, qtwebengine_resources.pak and icudtl.dat into Resources/
- QtWebEngineProcess into its own .app bundle, itself into Helpers/

QMAKE_BUNDLE_DATA is used to copy files into the bundle while INSTALLS is
used when installing normally. A LOCALE_LIST is explicitly listed since
QMAKE_BUNDLE_DATA can't handle the * glob to match all source files.

Change-Id: I5c0df57b4b9e93f9cce34a74a6e024bf90d37b5c
Task-number: QTBUG-41611
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

core_module.pro is the one responsible for deployment of the binary so
it makes sense to also let it handle the other files to install.

This leaves core.pro to only handle sub-projects dependencies.

Change-Id: Ibe433eceec7fb0a9f806dfa89dccb0bedeaccc59
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

The default size causes qt.io to look bad and is too small
for high resolution screens.

Change-Id: Ie417dde8ab32fc4897cd60c292afdc39b9213510
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: Id2e62af31f1dc5268fe6b163d2fc0b671f5e491a
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I528b7c4c22a1c47f54fe1b78a9d781a6af9cfc6b
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>

Change-Id: Id54fd7ca704bd9456c98765afdbaf04e3d46b33c
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>

This avoids using a General matrix for tile transformations which are
usually only translations in our case.

Change-Id: Ic947d7ef9b78de6d5d16ea718cc03255e38a8097
Reviewed-by: Michael Bruning <michael.bruning@digia.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This should help users understand which prerequisites are
missing from their system and may also help find invalid CI
configuration quicker.

Change-Id: If564825c11782b6e760f016893010008d9a551fa
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Adds a test to check the return types of runJavaScript.

Change-Id: Ifd0cb4adf57c972e8a8ad240d51f11f0cc17aa3d
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I935ee10d10248ab525aca31c1b1c04d2927915c1
Reviewed-by: Michael Bruning <michael.bruning@digia.com>

The Windows command shell try to interpret the single quotation mark
as a command.

Change-Id: I4dc4382bdbe0c90565f6ac56c33a80971669344c
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Michael Bruning <michael.bruning@digia.com>

QtWebEngine::initialize happens after QGuiApplication instantiation,
so it is too late to simply set the application attribute.
In that scenario, we don't want to override the shared context and risk
a double free when both QGuiApplication and our cleanup handler try
to delete it.

Change-Id: Id52884abbb0c2380208876d9c00e8ddbfbc21eda
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Use explicit url in quick API too and use GetLastCommittedURL instead of
GetVisibleURL for getting the expected urls in tests.

Change-Id: If3251323645979643f3dc0e16491fe35b584f51c
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This fixes 7639513f

.

Change-Id: I512ca97d8b4fc8b7c48f03ab32d476bb3a791157
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

Adapt test results to the chromium behavior and remove expected
failures.

Change-Id: I277462125822e50f84c0d0ae795846a71c9a2b10
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

The GCC version check is only run on Linux.
Change-Id: I524508d763005190764526ce337dc348e5ba4fcb
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>

Chromium is only supported on ARMv6 and ARMv7 for ARM architecture.

Change-Id: I0493c9ba2baf4a537f759286622056093c0d4a25
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

The build did not work when configuring to linux-g++-64,
although the platform is supported.

Task-number: QTBUG-41918
Change-Id: If2c8a5722d7d6b0ca28a99763531d8ffd9534de7
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This prevents the crash when a webpage requests geolocation permission.

Change-Id: I7331b869ec1439d678cee7941691289220718f3d
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

The snapshot ninja may cause issues in some environments, where a different
ninja version may work. If the user has NINJA_PATH set in their environment,
prefer that over bootstrapping our own.

Change-Id: I4c6d2f479aeae1f5137705ed2deb995b59ea287a
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I91ce455ac5e3992e50d13c14f4035f91baad85bf
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Task-number: QTBUG-41952
Change-Id: Ic21089a34364696c8ff7e68e397e39f8f0b7f5cc
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This fixes cross-compile settings detection for cross-compilation
environments where the C compiler cross-compilation flags are set in
CC/QMAKE_CC instead of CFLAGS/QMAKE_CFLAGS (e.g. OpenEmbedded).

Change-Id: I0a7b0f6c47a00775ec18073a16359c8351363285
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I972d3560d6aa2640a2702f219cf802d2476b1c6e
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

That code was borrowed straight from Chromium and used the Chromium
coding style.

Change-Id: I212aea23f19056b901cbc770640faed4998f02fd
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This is required so that embedders can implement custom error pages,
and is also needed for tests, where error-page loading has side-effects
on subsequent page loads.

Change-Id: I5ae276a58864a2fa9d7b608bea3340b482a92f4e
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>

This should be removed once desktop notifications
have been implemented.

Task-number: QTBUG-41893
Change-Id: Ia004ee8946ae4441027161f5dddf05d304df8b1b
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: Ie27e4af5f4517bb1e1eea1262ab32140b3dff816
Reviewed-by: Andras Becsi <andras.becsi@digia.com>