Commit 4c4698fd authored by Allan Sandfeld Jensen's avatar Allan Sandfeld Jensen
Browse files

Update changes-5.11.2


Add a few missed changes from 3rdparty

Change-Id: Ie503da76d20440729516224c48bf0c95aade66d7
Reviewed-by: default avatarJüri Valdmann <juri.valdmann@qt.io>
Showing with 6 additions and 0 deletions
...@@ -55,6 +55,7 @@ General ...@@ -55,6 +55,7 @@ General
------- -------
* [QTBUG-59891] Popups are now closed when parent window is moved. * [QTBUG-59891] Popups are now closed when parent window is moved.
* [QTBUG-67801] Fixed assert with some AMD CPUs on Windows.
* [QTBUG-68699] Fixed another crash with non-integer Qt scaling. * [QTBUG-68699] Fixed another crash with non-integer Qt scaling.
* [QTBUG-69231] Fixed keyboard modifiers on drop events. * [QTBUG-69231] Fixed keyboard modifiers on drop events.
* [QTBUG-69236] Fixed --enable-webgl-software-rendering to ignore blacklist * [QTBUG-69236] Fixed --enable-webgl-software-rendering to ignore blacklist
...@@ -63,10 +64,15 @@ General ...@@ -63,10 +64,15 @@ General
* [QTBUG-69372] QWebEngineUrlRequestJob::initiator() now differs * [QTBUG-69372] QWebEngineUrlRequestJob::initiator() now differs
between unique origins and unknown origins. between unique origins and unknown origins.
* [QTBUG-69605] HSTS state is now persistent with appropriate profiles. * [QTBUG-69605] HSTS state is now persistent with appropriate profiles.
* [QTBUG-69639] Work around MSVC compiler error affecting printing on
32-bit Windows.
* [QTBUG-69904] JavaScript worldID can now be up to 256 (up from 11), * [QTBUG-69904] JavaScript worldID can now be up to 256 (up from 11),
and the limit is now documented. and the limit is now documented.
* [QTBUG-70034] Fixed qtwebengine_convert_dict failing on certain
dictionaries.
Build Build
----- -----
* [QTBUG-50554] Update libvpx check to match standard versions. * [QTBUG-50554] Update libvpx check to match standard versions.
* [QTBUG-69121] Fixed shadow builds on read-only sources.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment