Skip to content

Commit 594e2b7

Browse files
author
Qt Forward Merge Bot
committed
Merge "Merge remote-tracking branch 'origin/5.12.5' into 5.12"
2 parents d5d0cd8 + 2f4675e commit 594e2b7

File tree

1 file changed

+80
-0
lines changed

1 file changed

+80
-0
lines changed

dist/changes-5.12.5

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
Qt 5.12.5 is a bug-fix release. It maintains both forward and backward
2+
compatibility (source and binary) with Qt 5.12.0 through 5.12.4.
3+
4+
For more details, refer to the online documentation included in this
5+
distribution. The documentation is also available online:
6+
7+
https://doc.qt.io/qt-5/index.html
8+
9+
The Qt version 5.12 series is binary compatible with the 5.11.x series.
10+
Applications compiled for 5.11 will continue to run with 5.12.
11+
12+
Some of the changes listed in this file include issue tracking numbers
13+
corresponding to tasks in the Qt Bug Tracker:
14+
15+
https://bugreports.qt.io/
16+
17+
Each of these identifiers can be entered in the bug tracker to obtain more
18+
information about a particular change.
19+
20+
****************************************************************************
21+
* Qt 5.12.5 Changes *
22+
****************************************************************************
23+
24+
General
25+
-------
26+
27+
- [QTBUG-62106] Fixed possible crash after rapid tapping.
28+
- [QTBUG-75884] Fixed crash on setHttpUserAgent.
29+
- [QTBUG-76249] Fixed user-agent on some new windows.
30+
- [QTBUG-76268] Fixed tab key send on minimize.
31+
- [QTBUG-76347] Fixed duplicate events being send from tablets.
32+
- [QTBUG-76828] Clear shared context on exit.
33+
- [QTBUG-76958] Fixed possible crash when loading in background.
34+
35+
Chromium
36+
--------
37+
38+
- Security fixes from Chromium up to version 76.0.3809.87, including:
39+
40+
- CVE-2019-5829
41+
- CVE-2019-5831
42+
- CVE-2019-5832
43+
- CVE-2019-5837
44+
- CVE-2019-5839
45+
- CVE-2019-5842
46+
- CVE-2019-5851
47+
- CVE-2019-5852
48+
- CVE-2019-5854
49+
- CVE-2019-5855
50+
- CVE-2019-5856
51+
- CVE-2019-5857
52+
- CVE-2019-5860
53+
- CVE-2019-5861
54+
- CVE-2019-5862
55+
- CVE-2019-5865
56+
- Critical security issue 977057
57+
- Security bug 934161
58+
- Security bug 939644
59+
- Security bug 948172
60+
- Security bug 948228
61+
- Security bug 948944
62+
- Security bug 950005
63+
- Security bug 952849
64+
- Security bug 956625
65+
- Security bug 958457
66+
- Security bug 958689
67+
- Security bug 959193
68+
- Security bug 959518
69+
- Security bug 958717
70+
- Security bug 960785
71+
- Security bug 961674
72+
- Security bug 961597
73+
- Security bug 962083
74+
- Security bug 964002
75+
- Security bug 973893
76+
- Security bug 974627
77+
- Security bug 976050
78+
- Security bug 981602
79+
- Security bug 983850
80+
- Security bug 983938

0 commit comments

Comments
 (0)