Change-Id: I3638fd51bbb871b7dc920a7c3e1435c26db02f7c
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>

An adaptation to Chromium 70 caused a regression in this.

Change-Id: I8928694b9f99cd420afd858d3a1023228276bae0
Reviewed-by: Kirill Burtsev <kirill.burtsev@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

When UI and GPU threads are the same we not need to do async scheduling
or calls between them, and doing so comes at a much higher cost than
in a multithreaded environment.

Change-Id: Icddee1a78d87ce08362882da5740471dfef1224a
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

This was changed as an adaptation to Chromium 70, but turns out
to be causing some regressions.

Updates Chromium to include the changes there.

Change-Id: I1e507bc2c51975c85afccd4346b02c43f5a44478
Fixes: QTBUG-74847
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Add scheme checks for FilePickerController::accepted().
A file:// prefix to a file selected here causes chromium to terminate
the render process due to an illegal ipc message.

Extend auto tests with custom Dialog.

Also fix directory upload test.

Change-Id: I8d672e435129d62d268b48c3471b924c0161b44b
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

It should be rather skipped than blacklisted since it is not expected to
work on Windows.

See the corresponding warning about ACLs:
https://doc.qt.io/qt-5/qfile.html#setPermissions



Task-number: QTBUG-74698
Change-Id: Iad66c028583d6811b7a413dd9800e9095d8f6da7
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Change-Id: I1dc8b466d0b45f9e1d6c973f1ad3c62033bf4409
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

Chromium requires us to add a special config to enable precompiled
headers. Note this still depends additionally on that the corresponding
GN flag is also set.

Changes in 3rdparty:
9401dc18ce02 Add precompiled object files to qmake link output
8ba90427ae5e Improve the issue with long file names on windows

Change-Id: I6680232e17a5254d3ca53e5a40e6a15a6b7fc82d
Reviewed-by: Michal Klocek <michal.klocek@qt.io>

Task-number: QTBUG-74764
Change-Id: I0e872449584b37c484e4d5ea46ba0bbc47124f51
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Conflicts:
	src/3rdparty
	src/core/renderer/user_resource_controller.cpp
	src/core/web_contents_adapter.cpp
	src/webengine/doc/src/qtwebengine-overview.qdoc

Change-Id: I46be9d33b3b65d61dfa099ee72a3509afb9bd6a4

Also make the number more general as we will be updating the patch
number at least once more before final.

Change-Id: Ie9bfffb8f87fdb2c08a416ca1b977f7b0afc8c32
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

Fixes regression, introduced by the fix for QTBUG-66011, where setting
JavascriptEnabled to false stops all scripts from running instead of only
MainWorld scripts (as documented). Only the DocumentCreation injection point is
affected.

The original change which introduced the regression consisted of moving the
DocumentCreation injection point from

    ContentRendererClient::RunScriptsAtDocumentStart

to

    RenderFrameObserver::DidClearWindowObject.

The problem of scripts not working on view-source URLs was fixed by this move,
but it turns out that the call to DidClearWindowObject happens to be conditional
on Document::CanExecuteScripts and this is, of course, false if JS is disabled.
Hence the regression.

This new patch moves the injection point again to a task launched from

    RenderFrameObserver::DidCommitProvisionalLoad.

DidCommitProvisionalLoad and DidClearWindowObject are both indirectly called
from DocumentLoader::InstallNewDocument, however the former is called before the
Document is opened and is therefore too early for script execution. As such, the
execution is delayed by posting a task which, in theory, should be scheduled
very soon after the normal call to DidClearWindowObject.

Fixes: QTBUG-74304
Change-Id: Iac8714bcc5651c287b73181811af26996d955af5
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Changes:
2cdff75f3db Fix crash in devTools layer tab on qt.io
f72214e77a7 BASELINE: Update Chromium to 73.0.3683.105
d8e950cba2f Merge branch 'upstream-master' into 73-based

Change-Id: I5eed1b0e4858254a7a74fbc5f9940dea4fbf1367
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

Task-number: QTBUG-74698
Task-number: QTBUG-74251
Change-Id: I4358feb7fb28b226edb24ed10611e797fcd3c326
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Change-Id: I8a087fefcb9f0f1c750747d29819e53c11984b41

Task-number: QTBUG-74543
Change-Id: Ice5a0dbfc3485c8b7e6fa900ef427a9aed871d42
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Pulls in security patches:

* [Backport] Security bug 933743
* [Backport] Security bug 917608
* [Backport] Security bug 916874
* [Backport] Security bug 914511

Task-number: QTBUG-74445
Change-Id: Id1ad904857e8f8e15208ae80c8c0258e3d8f4faa
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Chromium returns unexpected proxy reply if localhost is used.

Since proxy resolver works now, the workaround to trigger dialog
with "localhost proxy" can be skipped.

Change-Id: I26d88c43779809e4f481101266e6b8784a6b196d
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Task-number: QTBUG-72113
Change-Id: I9b2dfb360a18995cae9e0e4a98443e796c3d8ad0
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Wait to finish javascript execution before opening
next dialog.

Task-number: QTBUG-72113
Change-Id: I383e3fc3c405a94ddcbd74fe1cc7ab0d81c4e315
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Change-Id: I8806a3fb466006f14cf92f17510cdea8b50e8345
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

Follow similar Chromium changes.

Change-Id: Idb0ab52517004c8bee7e7f7a919233b3f1b3ff59
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

Following https://chromium-review.googlesource.com/1074753



Change-Id: Idba6062b978fcff07d6fcb827d863605f06fcf9f
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

Change-Id: I348fd097db179557d04cde224f6a49f0d1c2f97d
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

Also fixes the fact that WebEngine was passing POST data to Chromium
even if the request was not a POST request. This triggered an assert
in the backported code.

3aaf2ca833c [Backport] Security bug 906739
e4e10461659 [Backport] Security bug 906437
0a717e1dbe9 [Backport] Security bug 913212
c7fa9a16957 [Backport] CVE-2019-5803
ebe1e7068ca [Backport] Dependency for CVE-2019-5802 (1/5)
597dae52a3b [Backport] CVE-2019-5802 (1/5)
64d3770e5e9 [Backport] CVE-2019-5802 (2/5)
a34d2fb5dd1 [Backport] CVE-2019-5802 (3/5)
62f25b2d83f [Backport] CVE-2019-5802 (4/5)
a63d51633ab [Backport] Dependency for CVE-2019-5802 (5/5)
c6d0023bc59 [Backport] CVE-2019-5802 (5/5)
f7fcbe53871 [Backport] Security bug 905509 (1/13)
94f1317917f [Backport] Security bug 905509 (2/13)
812a9e68a2c [Backport] Security bug 905509 (3/13)
36c2c5e8b27 [Backport] Security bug 905509 (4/13)
8b01fa3780a [Backport] Security bug 905509 (5/13)
69b772f1e9a [Backport] Security bug 905509 (6/13)
f2dfd87785a [Backport] Security bug 905509 (7/13)
ec503eae3ed [Backport] Security bug 905509 (8/13)
f5a4144a132 [Backport] Security bug 905509 (9/13)
03d8580cf59 [Backport] Security bug 905509 (10/13)
03c4a4ffb98 [Backport] Security bug 905509 (11/13)
700a4af1fb5 [Backport] Security bug 905509 (12/13)
03be3aa656a [Backport] Security bug 917707
269d53ceabd [Backport] Security bug 905509 (13/13)
d720564a5ba [Backport] Security bug 938251
85136fedbde [Backport] Security Bug 929088
037efcfdba3 [Backport] Security Bug 931640 1/2
bea83ccee0f [Backport] Security Bug 931640 2/2
dd18af1614f [Backport] Security Bug 924905
e54c1076009 [Backport] Security Bug 919572
258feedf8e1 [Backport] Security Bug 919340
f4f1e852df5 [Backport] CVE-2019-5789
8566ec6cc21 FIXUP:  [Backport] Security bug 905509 (3/13)
3d59c5717de FIXUP: [Backport] Security bug 906739
dd6863f4aea FIXUP: [Backport] Security bug 905509
43c92056fab FIXUP: [Backport] CVE-2019-5802
d6d21a17c5a FIXUP: [Backport] Security bug 913212
a4a129005d8 FIXUP: [Backport] Security bug 905509
38a6ae037ee FIXUP: [Backport] Security Bug 924905
d147ad350da FIXUP: [Backport] Security bug 905509 (3/13)

Task-number: QTBUG-74445
Change-Id: Ic8d750bc89950c0e020eb43881dbf03328108940
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Changes:
b7c3aa56eca9 Fix linking issue on some Linux builds
72b4b6fc4ee4 Remove assert on exit
6c2d06e60643 Fix Windows 32bit build
3d95374cb8de FIXUP: Fix Windows 32bit build

Task-number: QTBUG-74854
Change-Id: Ifcf946b034a21a5263776ac1950700ce45e782f3
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Remove the previous workaround (internal \externalpage command) that
was used for this purpose, and replace it with a \QWE macro that
expands to the string 'Qt \WebEngine'. The backslash in the expanded
string instructs QDoc not to attempt auto-linking the word.

Change-Id: If4e1c95423fa07479b1af055e4760a890c0ac667
Reviewed-by: Paul Wicking <paul.wicking@qt.io>

Add a newline after the module title, like it is done for other modules.
Also call the module "WebEngine", not "Webengine".

Change-Id: I78579fb0ab131373212ea302eb5d3e5dd9cc62ca
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Qt expects the export macros to have Q_ prefixes, otherwise the symbol
versioning script won't find them and mark them.

Task-number: QTBUG-74752
Change-Id: I1e057802f6715d170bdd9074f281e73fb96c9e52
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Kai Koehne <kai.koehne@qt.io>

Change-Id: I472ff20de710b1300c1f5209f3100b5280356f45
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

We do require at least harfbuz 2.2
We need hb-aat.h for opentype.

Change-Id: Ia2814de6045884b4574ee6c55e74f04005321ac2
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Task-number: QTBUG-74764
Change-Id: I2638a6857e1d29ebacaafac3fff5daab57268b54
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

This is our most flaky test at the moment

Task-number: QTBUG-74718
Change-Id: Ia7668347a74982abfb0297169f564db89944e87c
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Based on https://chromium-review.googlesource.com/c/chromium/src/+/1432882



Task-number: QTBUG-74764
Change-Id: I74b4711f5146d2d2261487f13ccac702b9aa969e
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Conflicts:
	.qmake.conf
	src/3rdparty
	src/core/render_widget_host_view_qt.cpp
	src/core/web_contents_view_qt.h
	src/core/web_engine_context.cpp

Change-Id: I17f3a4814e88a5680dc61a6d734c171ccba00e8c

Change-Id: I671e02850109e26c60771f583a3b5f29a1220452
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

Offscreen plugin tries to open opengl handle and fails.
Disable test for now.

Change-Id: I6cecfef4e47a700ff720811f8e8dc4829a814821
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

It is the host side of RenderViewObserverQt in the renderer dir, so
should be in the renderer_host dir.

Change-Id: I497a6442130993237a0b823e7dcdd121bd72355a
Reviewed-by: Michal Klocek <michal.klocek@qt.io>