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>

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>

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

Needs some cleanup to do comparisons FS-agnostic, and is currently
blocking.

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

The modern media controls in 69-based were not completely ready, so
stay with the legacy media controls until 5.13.

Fixes: QTBUG-74484
Change-Id: I06de16d8210341443a10d8c984f1978d373de0d9
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

Go back to making the tooltip richtext, but set a white-space:pre to
keep the tooltip mostly unwrapped.

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

Pulls in security patches:

* [Backport] CVE-2019-5787
* [Backport] Security bug 906652
* [Backport] CVE-2019-5797
* [Backport] Dependency for CVE-2019-5797 2/2
* [Backport] Dependency for CVE-2019-5797 1/2
* [Backport] CVE-2019-5795

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

Necessary adaptation to 73-based. Triggers initialization of V8 exten-
sions and prevents hitting CHECK due to unintialized safe_builtins when
loading a PDF.

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

Some things controlled by the OFFICIAL_BUILD defined are commented as
unsafe to ship in production, so we need that as well.

Note that GOOGLE_CHROME and OFFICIAL_BUILD are two different settings,
so this just denotes the build as one shipped in production.

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

In what almost seems like intentionally confusing terminology, Chromium draws a
distinction between the UI thread and UI type threads. The thread's type refers
mainly to the MessagePump implementation that it uses: currently
MessagePumpForUIQt for all UI type threads.

It turns out however that the desktop capture thread on macOS requires the
original MessagePumpMac implementation for some macOS specifics. So, with this
patch, MessagePumpForUIQt will be used only for the actual UI thread, and all
other UI type threads will use upstream message pump implementations.

Theoretically, this means that we cannot send events or async signals to these
other UI type threads any more (sending events *from* these threads should still
work). Practically though it seems safer to try, as far as possible, to not mix
different event/task frameworks on the same thread.

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

BrowserDataRemoverImpl::Remove() indirectly calls
TransportSecurityState::DeleteAllDynamicDataSince() which notifies by
a callback about the finished deletion since:
https://chromium-review.googlesource.com/c/chromium/src/+/1335939



During the deletion the ProfileIODataQt::requestStorageGeneration()
should not be called because it deletes net::TransporSecurityPersister
which background_runner is where the finished deletion callback is
scheduled.

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

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

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

This logic was incorrectly stripped out in adaptations
for Chromium 68, but is still needed.

Fixes: QTBUG-74519
Change-Id: Iefe7aba352bd43148898c1abeea34f4afe354d72
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>

The new version of WebEngineSettings wasn't registered

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

Apparently not having a newline before each recipe title, prevented the
markdown JS renderer from rendering the titles properly, instead the
titles wee unformatted and also displayed the = signs.

Add the new lines.

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

Follow the other implementation and pass TakeFocus to WebContents
Delegate, and hook to our UI from there. Also fixes use of Blur instead
of LostFocus, which means we now render unfocused more correctly.

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

Fixes: QTBUG-55146
Change-Id: I034ebb3e65341b5424a24d5a143013d726d55e10
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

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

Change-Id: I353693b039d5ce923db1d18d5da15db1ae714e71

Was switched to build-flags, and enums renamed

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

It is now only possible to list contained certificates, which is used
by the existing tests.

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

Change-Id: If0a4c869d801fe94df23201391c30c1efc5000e0

PDFViewerEnabled is renamed to PdfViewerEnabled.

Task-number: QTBUG-74543
Change-Id: I48a242a52ab0689b06815ac3cbd98c44902cc358
Reviewed-by: Kai Koehne <kai.koehne@qt.io>

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

Fixes false navigation type on http-equiv refresh, and javascript
redirects.

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

Pulls in security patches:

* [Backport] CVE-2019-5794
* [Backport] CVE-2019-5793
* [Backport] CVE-2019-5792
* [Backport] CVE-2019-5791
* [Backport] CVE-2019-5790

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

Action point from the API review.

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

Using SetInteger prevents release check: 'Trying to set pref
persistent_notifications.next_id of type integer to value of type
string'. This also mimics chromium notification service code.

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

Change-Id: Icd8a5966a160e2466dc32a89d4ed7d904a3bcb4c

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

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

Add some tests which looks stable enough and do
not require blacklisting.

Task-number: QTBUG-63346
Change-Id: I071669895f6c81af498b5348ef86d81d551c899d
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

Pulls in latest security fix from 72 releases, one which is actively
exploited.

Fixes: QTBUG-74254
Change-Id: Iaef4cecb15295e45a795bc37cc1b467de5cc7bc1
Reviewed-by: Michal Klocek <michal.klocek@qt.io>