This will only contain free codecs.

Change-Id: I021b2c121bf146abb24b7a90dd1c3580638b1058
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

The prompt dialog inherits ApplicationWindow, which emits the
signal "closing" when the window gets closed by pressing the X
button.

Change-Id: I23e5cf6f8e81251869d765d7fd2864257f3c0b89
Task-number: QTBUG-43902
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

Change-Id: I772c9710d8b01efd385a54e5f642ae2b62702a0e

For dependencies that have caused trouble before, such
as libdrm.

Task-number: QTBUG-41516
Change-Id: I0cee98282e93460971471796a65a43be4750c6b0
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

Move the logic to mkspecs to keep the .pro files robust.

Add the basic infrastructure for config.tests, the first one
of which will consistently ensure we have libcap on linux.

Change-Id: Iee4207e747e589ba67d5353cb4c18f156e555c11
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

We shouldn't hardcode to a particular branch there.

Change-Id: I9cab855363cfaaa3d8d31879b0c459697a4a6f4c
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

This will avoid printing the compiler version python was built with.
Showing the compiler version led to confusion multiple times.

Change-Id: I4ced2128b92c83a41f616bcf756f2c313a9caed3
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

Fixes crashes of the QtWebEngineProcess on OS X 10.7 that were
caused by the bundle paths not being returned correctly.

Change-Id: Ic839978a6f1bff361cb76a3468bf978a738b6e82
Task-number: QTBUG-43181
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

This mitigates the risk of the POODLE vulnerability.

Updates the 3rdparty submodule SHA1.

Change-Id: I7557ecfd5f4f250a51e18432936b83502ba5d272
Task-number: QTBUG-43085
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

Otherwise gyp will use it's own sysroot (which doesn't exists)
if you are doing a croos-build without using the --sysroot configure option

Updates the src/3rdparty SHA1.

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

This reverts commit a7da7f8a

.

Adding the install prefix to the inlude search paths causes us to pick up
header files from there if there are any, which causes all sorts of issues.

Conflicts:
	lib/lib.pro
	shared/shared.pro

Change-Id: I070ff6443bb5612b3b7e3878d22dc9dd69d62e70
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>

It was previously ignored for Desktop Linux.

Change-Id: I214171d222a5e7e0ee64afde225a742adbda4adf
Task-number: QTBUG-43387
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

This prevents problems when QProcess::waitForFinished is used from the
same application as QtWebEngine.

Updates the src/3rdparty SHA1.

Change-Id: I373456b1ef9f65e55b89acd877b15e7115516d6b
Task-number: QTBUG-42747
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

This moves all installs inside the the release-only-with-debug-fallback
block to prevent the debug ffmpegsumo.dll to overwrite the release
one on Windows (and get use for both debug and release builds).

This will use the release version for both instead by default.

This also moves the load(qt_module) call higher to make sure that
build_all is added to CONFIG at that point.

Change-Id: I2584a28e5eaaf5028798703fb387ac2b120d7ea9
Task-number: QTBUG-43348
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

qmake may have quoted already because of certain characters like ~ in
build path

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

This doesn't seem to be too much sense, and according to the QQmlContext
documentation, may not work as expected: "This is only valid for components
created directly from QML."

Change-Id: I49db5dad49288d196e8519b1a60dcf2192147672
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>

If the dialog controller has asked to show a dialog, then if we cannot show a
dialog, we should reject its request.

Not doing this results in the WebView becoming frozen for input if the load
fails, seemingly.

Change-Id: I7dddd5357c712f896499cdebb142e60b5e80b4f2
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>

This setting is useful when developing a new UI set, and one may not initially
know about the suppression of errors, which is a painful problem to run into.

Furthermore, make sure to delete the failed component so that subsequent
attempted use of it doesn't succeed if UI_DELEGATES_DEBUG isn't enabled.

Change-Id: I3d2abc19fb4a007d06795d2e8149ae78d7c9c020
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>

Change-Id: I155088b491e86d12eccf3c131acf9aad2dfd2a14

Change-Id: Id7afc11cd58f671ff5ce629cfc29bdb6d9567dc2
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>

As QtWebEngine now uses 5.x as its version number, we can just
provide cmake tests and let qmake scripts do the rest.

Task-number: QTBUG-42073
Change-Id: I28ccddbd1849980074dfbeefb5cb5a70c9209ab1
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

Change-Id: Id56d08a3b3192c63ee6d2f56cee8085ed41ac666

This fixes the focusing issues on touch devices.

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

We create an EGL_KHR_fence_sync on the chromium thread
but try to verify if the wait function implementation
is available by testing for the EGL_KHR_reusable_sync
extension in the scene graph thread.
Since the latter extension is not supported by most of
our devices, we never actually waited for the rendering
to finish.

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

This prevents the crash when the application requests
persistent storage access using the Quota API (e.g. on
http://codepen.io/matt-west/full/CrfKh

). The request has been
disallowed for now, because it should rely on user permission.

Change-Id: I4ae057c9485d3f06f45a637c7eeda9dd69fe6b54
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>

Without the class description the methods documentation was never
generated.

Change-Id: I0d7232e8f5cc6765908cb28b77d0fe0f514d359d
Task-number: QTBUG-42996
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Cookies were not flushed on application exit because objects deleted
lazy on the UI-thread never had their destructors called because we
did not flush the queue on exit.

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

Set the LSUIElement key as Chromium does in its helper app's
Info.plist to prevent seeing a jumping icon in the dock while the OS
waits in vain for QtWebEngineProcess to create a window.

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

This fix deploys the following files into qtbase without make install:
- qtwebengine_resources.pak
- translations/qtwebengine_locales/*.pak
- icudtl.dat
- plugins/qtwebengine/libffmpegsumo.so

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

Change-Id: I2c48688f5f034233660bd7891693f81525fc1d6d

Since we use the system ICU we do not need the extra data file.
This fixes a crash caused by missing icudtl.dat file.

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

Until we can rely on Qt using @rpath on OSX, QtWebEngineProcess'
dependencies must either be updated by macdeployqt when creating
an .app bundle, either we must make that path relative at build
time.

Since QtWebEngineProcess.app is always deployed inside
QtWebEngineCore.framework, we can safely assume that the dylib is
always in a parent directory and that QtCore.framework can be found
one directory higher.

The additional dependencies of QtWebEngineCore.framework will be
handled by the dynamic linker when it gets loaded, but this only
works for QtWebEngineProcess when macdeployqt uses @loader_path
instead of @executable_path (then relative to the application which
is in a different directory than QtWebEngineProcess).
This can be forced by passing a non-empty value for its
-executable= command-line argument (e.g
`macdeployqt Browser.app -executable=Browser.app/Contents/MacOS/Browser`)

All this will be much simpler once we got Qt framework builds to use
@rpath instead in a future minor version.

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

    - Add documentation for Quick Nano Browser
    - Add all examples to the correct group
    - Add instructions to run the examples
    - Qt WebEngine Widgets index page: Add examples section

Task-number: QTBUG-42668
Change-Id: Ie60f8708336b9c147d0c22afb555fe87287deddc
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>

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

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>