Merge remote-tracking branch 'origin/5.13.1' into 5.13

Change-Id: I23368e20be22e833368818008e741e1f0d2cfb4a

2 files changed, 94 insertions, 1 deletions

diff --git a/dist/changes-5.13.1 b/dist/changes-5.13.1
new file mode 100644
index 000000000..9e3a49558
--- /dev/null
+++ b/dist/changes-5.13.1
@@ -0,0 +1,91 @@
+Qt 5.13.1 is a bug-fix release. It maintains both forward and backward
+compatibility (source and binary) with Qt 5.13.0.
+
+For more details, refer to the online documentation included in this
+distribution. The documentation is also available online:
+
+https://doc.qt.io/qt-5/index.html
+
+The Qt version 5.13 series is binary compatible with the 5.12.x series.
+Applications compiled for 5.12 will continue to run with 5.13.
+
+Some of the changes listed in this file include issue tracking numbers
+corresponding to tasks in the Qt Bug Tracker:
+
+https://bugreports.qt.io/
+
+Each of these identifiers can be entered in the bug tracker to obtain more
+information about a particular change.
+
+****************************************************************************
+*                              Qt 5.13.1 Changes                           *
+****************************************************************************
+
+General
+-------
+
+  - [QTBUG-62106] Fixed possible crash after rapid tapping.
+  - [QTBUG-76226] Fixed PDF viewer on URLs with percent-encoded characters.
+  - [QTBUG-76249] Fixed user-agent on some new windows.
+  - [QTBUG-76958] Fixed possible crash when loading in background.
+
+
+Chromium
+--------
+
+ - Security fixes from Chromium up to version 76.0.3809.87, including:
+
+    - CVE-2019-5829
+    - CVE-2019-5831
+    - CVE-2019-5832
+    - CVE-2019-5836
+    - CVE-2019-5837
+    - CVE-2019-5839
+    - CVE-2019-5842
+    - CVE-2019-5851
+    - CVE-2019-5852
+    - CVE-2019-5854
+    - CVE-2019-5855
+    - CVE-2019-5856
+    - CVE-2019-5857
+    - CVE-2019-5860
+    - CVE-2019-5861
+    - CVE-2019-5862
+    - CVE-2019-5865
+    - Critical security issue 977057
+    - Security issue 934161
+    - Security issue 939644
+    - Security issue 948172
+    - Security issue 948228
+    - Security issue 948944
+    - Security issue 950005
+    - Security issue 952849
+    - Security issue 954762
+    - Security issue 956625
+    - Security issue 958717
+    - Security issue 958457
+    - Security issue 958689
+    - Security issue 959192
+    - Security issue 959193
+    - Security issue 959518
+    - Security issue 960785
+    - Security issue 961597
+    - Security issue 961674
+    - Security issue 962083
+    - Security issue 962572
+    - Security issue 964002
+    - Security issue 964795
+    - Security issue 964928
+    - Security issue 973893
+    - Security issue 974627
+    - Security issue 976050
+    - Security issue 981602
+    - Security issue 983850
+    - Security issue 983938
+
+
+Qt WebEngine Core
+-----------------
+
+ - [QTBUG-60203] QWebEngineUrlRequestInterceptor can now set referer header.
+
diff --git a/src/webengine/doc/src/qtwebengine-features.qdoc b/src/webengine/doc/src/qtwebengine-features.qdoc
index 08c189740..00b9cb496 100644
--- a/src/webengine/doc/src/qtwebengine-features.qdoc
+++ b/src/webengine/doc/src/qtwebengine-features.qdoc
@@ -126,7 +126,9 @@
     so uniquely identifies the user and might violate privacy expectations.
 
     To activate support for client certificates, an application needs to listen to
-    the QWebEnginePage::selectClientCertificate signal and select one of the offered
+    the QWebEnginePage::selectClientCertificate or
+    \l{WebEnginePage::selectClientCertificate}{WebEnginePage.selectClientCertificate}
+    signals and select one of the offered
     certificates. For applications that can navigate to untrusted web sites, it is
     recommended to always give the user a choice before uniquely identifying them
     to a remote server.