summaryrefslogtreecommitdiff
path: root/dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2024-08-13 20:06:33 -0400
committerIonen Wolkens <ionen@gentoo.org>2024-08-14 11:34:23 -0400
commit4e57d2b93959aa52fa3f6867d416e0469969d253 (patch)
tree294820c85483cfae4876eeed59721e8b87b6f9e2 /dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch
parent1a209033b6a4f7ed41cbb5e374064c802d0fe188 (diff)
downloadgentoo-4e57d2b93959aa52fa3f6867d416e0469969d253.tar.gz
gentoo-4e57d2b93959aa52fa3f6867d416e0469969d253.tar.bz2
gentoo-4e57d2b93959aa52fa3f6867d416e0469969d253.zip
dev-qt/qtwebengine: update 6.7 and 6.8 patchsets
6.7-10 -> 6.7-11, and 6.8-2 -> 6.8-3 changes: Added: * clang19.patch (imported from files/) * musl-no-settls.patch (wrt bug #937875) 6.7-10 -> 6.7-11 specific changes: Added: * QTBUG-113574.patch (imported from files/) 6.7-11 -> 6.7-12 changes (in preparation for 6.7.3): Removed: * ninja1.12.patch (upstreamed) Technically needs a revbump for bug #937875 (runtime issue), but do not wish for every users to rebuild over a musl fix. musl users reading this are invited to `emerge -1 qtwebengine:6`. Stable users are not believed to be affected, and there's to hope 6.7.3 releases & is stabilized before musl-1.2.5 is (or a := forces a rebuild first). Closes: https://bugs.gentoo.org/937875 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch')
-rw-r--r--dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch41
1 files changed, 0 insertions, 41 deletions
diff --git a/dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch b/dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch
deleted file mode 100644
index d8a9158c8a01..000000000000
--- a/dev-qt/qtwebengine/files/qtwebengine-6.7.2-QTBUG-113574.patch
+++ /dev/null
@@ -1,41 +0,0 @@
-Backport of [1] from 6.8/6.9 for [2].
-
-[1] https://codereview.qt-project.org/c/qt/qtwebengine/+/569910
-[2] https://bugreports.qt.io/browse/QTBUG-113574
-
-From 21a9add47def34322b799683e1e1daff88dc4a06 Mon Sep 17 00:00:00 2001
-From: David Edmundson <davidedmundson@kde.org>
-Date: Wed, 19 Jun 2024 10:37:45 +0100
-Subject: [PATCH] Use device pixel ratio of the window rather than the screen
-
-Window device pixel ratio can differ from the screen depending on the
-platform. The window is the more authorative source with new events in
-Qt to support that.
-
-In Chromium the rendering is still based off a screen factor, but each
-view will have a completely independent set of screen variables, so we
-can adjust the screen to match our current view.
-
-Chromium itself also alters the screen scale factor on a per window
-basis for their own native Wayland backend or if recording a window.
---- a/src/core/render_widget_host_view_qt.cpp
-+++ b/src/core/render_widget_host_view_qt.cpp
-@@ -875,4 +875,9 @@
-
- display::ScreenInfos newScreenInfos = screenInfosFromQtForUpdate(window->screen());
-+
-+ // We always want to use the scale from our current window
-+ // This screen information is stored on a per-view basis
-+ auto &screen = newScreenInfos.mutable_current();
-+ screen.device_scale_factor = window->devicePixelRatio();
- if (screen_infos_ == newScreenInfos)
- return false;
---- a/src/core/render_widget_host_view_qt_delegate_item.cpp
-+++ b/src/core/render_widget_host_view_qt_delegate_item.cpp
-@@ -346,4 +346,6 @@
- onHide();
- }
-+ } else if (change == QQuickItem::ItemDevicePixelRatioHasChanged) {
-+ m_client->visualPropertiesChanged();
- }
- }