Changes:
8e6f5751e5 Restore media::FFmpegGlue::InitializeFFmpeg()
0c8d188f16 Add x86 target support for gn
2a52817b6e Fix creation of 'x86' toolchain in gn
3a84c2a8bc Add support for modules limiting jumbo width
c69fdae9c7 BASELINE: Update Chromium to 69.0.3497.113
3a783ba38b Merge remote-tracking branch 'origin/upstream-master' into 69-based
a4ecaddc7c Remove missing symlink to gen from perfetto/ui/src
3f8994c671 [Backport] Use newer GrGLFunction based on templated function types rather than pointers.

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

Calculates and uses the source rect of layers.

Task-number: QTBUG-67652
Change-Id: If5569da6e18a3b9728392ecf1f3c60e9e0663229
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

Get rid of old QSG type names, and also remove redundant setupTiledNode
call.

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

QWebEngineView now also emits url, title, icon and selection
changes on setPage in the save way when url changes. Before,
those updates were only forwarded from current page.

Fixes: QTBUG-69300
Change-Id: If827205094423bc00064a123ddb143b6002d2e7c
Reviewed-by: Kai Koehne <kai.koehne@qt.io>

Works with registered custom schemes, does not work with unregistered ones. In
the latter case the function call is treated as a security violation and the
renderer process is killed.

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

Change-Id: Id2a50e7b133e9b32150f3fd248e9822e1668fc13
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

The print-job manager was trying to recreate a notification service, so
destroy it earlier, and at the same time kill the content runner before
existing WebEngineContext::destroy() to catch any other late
recreations of singletons.

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

In preparation for a deeper cleanup to avoid mixing whitespace and non-
whitespace changes.

Change-Id: Iedbaf304a06b227799bbe74c71c570b7a675aea4
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

 Conflicts:
	configure.json
	configure.pri
	src/3rdparty

Change-Id: I2e0614b33596fe66999508556c464ed84acc8e2f

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

More security fixes from Chrome 69

Changes:
dd94e4234936 [Backport] CVE-2018-16066
9dec1e5d1048 [Backport] CVE-2018-16070
7610166df941 [Backport] Security patch 864932
9ffeaf4caa98 [Backport] CVE-2018-16076
af4500d25e07 [Backport] CVE-2018-16077
02d134e58d36 [Backport] CVE-2018-16083
22a79645f8d3 [Backport] CVE-2018-16085
8ea8f7a2e7ca [Backport] Security issue 867306
3b44cd3d8a9c [Backport] Security issue 867792
13aed800921e [Backport] Security issue 868592

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

Needed by chrome://accessibility



Updates chromium to related change:
224fc0748a Do not assert on --disable-gpu
0ba5e6626a FIXUP: Add ifdefs to exclude ATL and accessibility from the build

Change-Id: Ida0b03048ab6aa04686251d16ccfbf4855a37690
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

Channel ID is now default off in the params constructor, but still
default on as a feature in Chromium, but is deprecated and scheduled for
being removed and replaced with token-binding. This patch follows the
Chromium feature defaults for which of those is on or off.

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

Restore expected behavior for QWebEnginePage loading progress. This was
missing after queuing progress notification signals change. Add missing
state transition to loadSignalsOrder test.

Change-Id: Id1d94f8391b83decc8057c5108d2d19c38258965
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Michal Klocek <michal.klocek@qt.io>

Some files that the native spellchecker feature included were removed
after a reafctoring in Chromium.

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

Task-number: QTBUG-66871
Change-Id: I246d667dfe341a6bfe7a74b24286403bec4dde8b
Reviewed-by: Michal Klocek <michal.klocek@qt.io>

Task-number: QTBUG-68462
Change-Id: I6d3358d36bb3df91c05d434275e9c69682c982a9
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Michal Klocek <michal.klocek@qt.io>

Favicons are downloaded by the render process and sent back via mojo message.
However, mojo messages have a maximum size; if the favicon doesn't fit, the
render process is killed. Impose a maximum size to ensure that favicons can fit
in mojo messages.

Task-number: QTBUG-69123
Change-Id: I6027bc310dcc77ec530145e4f125efa36106464f
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>

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

We need to change surface id to acknowledge a resize is completed, and
we need to handle that Chromium is rejecting resize events because the
last one is not yet acknowledged.

Change-Id: I93b1e197218906de80d5748a5a100f7a740ea07c
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

Handle that Chromium now requires all wheel events to be phases despite
them not being phased on the majority of platforms.

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

Change-Id: I3980634a1029479ab944b2e03f12a02d0c77d0c1
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

Together-with: Tamas Zakor<ztamas@inf.u-szeged.hu>
Change-Id: I805246b6f01cb151fff48588744408c676d87c14
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

High security fixes from Chrome 69

Changes:
c92e99aa5f [Backport] CVE-2018-16067
38b701b44f [Backport] CVE-2018-16068
5adda98099 [Backport] CVE-2018-16071
021e3ee70e [Backport] CVE-2018-16072
cfc13dfc78 [Backport] Correctly handle blob:file:///

... URIs in SiteInstance::GetSiteForURL.
f1f5e7417e [Backport] Avoid unneeded call to Origin::GetURL from SiteInstance::GetSiteForURL.
c952ab2ef5 [Backport] CVE-2018-16074
ae14d10af6 [Backport] CVE-2018-16073
ebbf15c58c Update usrsctp

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

- Rename iconText to iconName
- Remove unused QQuickWebEngineAction::toggled signal
- Remove argument of QQuickWebEngineAction::enabledChanged signal

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

Conflicts:
	src/3rdparty
	src/core/core_common.pri

Change-Id: I36dc3a70aa653e6c8a610c787b615034180a6127

Either overlooked or added after we make the GN switch.

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

Change-Id: I7534aa6cd0c2a95403ad997095d5de76216f228e
Reviewed-by: Kai Koehne <kai.koehne@qt.io>

We have currently two levels of initialization for WebEngineView:
the profile initialization and the adapter initialization.

The adapter initialization is delayed to first navigation request
to pick the right initial site instance and avoid creating dummy/blank
WebContents, which in turn would start unnecessary render process.

Profile initialization is delayed to make sure we avoid unnecessary
default profile creations. Created profiles use filestorage. Unfortunately
qml will call QQuickItem::componentComplete() only when the root element
is completed and the bindings can be already in use by that time.

Profile initialization has to take place before adapter initialization.

Construct adapter together with WebEngineView, but create and initialize
profile before adapter initialization.

Go through WebEngineView and fix emitting signals based on adapter
initialization. Most of the signals are emitted on initializationFinished().

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

Following feedback from 5.12 API review:

- Use enum class for Syntax
- Add Q_FLAG for Flags
- Mark constructor from name as explicit
- Rename Secure to SecureScheme
- Rename Local to LocalScheme
- Rename addScheme to registerScheme
- Rename findScheme to schemeByName

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

Split compositing-related functionality from RenderWidgetHostViewQt into a new
class Compositor.

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

Change-Id: Idee34fa6d4cc54effd84d3b78e3666fa7fcce8db

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

We do not have it working together with the building of Chromium.

Task-number: QTBUG-66571
Change-Id: Ib000a4102b02902f2ac257347e406297fe1608cf
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>

Declare scheme name and about URL in one place.

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

It'll never pass unless the code is valid C++.

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

This pulls in the following changes:

* 79e2dad9 [Backport] Skip deleted object files in POSIX base::debug::StackTrace
* 3779b31a Fix hunspell::NodeReader::affix_id_for_leaf bounds check

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

Also fixes potential double delete if you do delete a view's implied
page.

Change-Id: Ib74128c0801f992694f4a5d8c148974039a6c7b2
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Reviewed-by: Zakor Tamas <ztamas@inf.u-szeged.hu>

Commit 83e790da

 removed the test, but
not the configure.json files, so the test always failed because the test
failed to compile.

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

Latin-1 is a standard fallback for HTTP headers, but no one that
HTTPContentDisposition::Parse considers by default.

Task-number: QTBUG-70288
Change-Id: Ife36fffe31da5492cde49a4d447cfc42b3f64b95
Reviewed-by: Zakor Tamas <ztamas@inf.u-szeged.hu>
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>