[qt/qt/qtbase]: Summary of bulk changes made
KDE Git Services - Bulk Change <[email protected]> Tue, 4 Aug 2026 12:16:06 +0000 (UTC)
| Newsgroups | gmane.comp.kde.cvs |
|---|---|
| Message-ID | <[email protected]> |
Git repository change summary for qt/qt/qtbase Pushed by mirror-service into branch '6.11'. Changed from 515710b7210e52d3182a1fb27abe4c9dbec8a43f to 6192d9edd00caa14ed6b67c32c0cd8cfe95cf815 Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository. This change contains the following new commits: Git commit 7edb2c33057c0e2bf01691726bf2c6c87e901d69 by Qt Cherry-pick Bot (on behalf of Jean-Michaël Celerier) on 04/08/2026 at 03:14.. stylesheet: fix build on windows when no style-windows feature Change-Id: I29f0bd2642c7b0db60a69809e1244aa6406ea752 Reviewed-by: Christian Ehrlicher <[email protected]> (cherry picked from commit 4e7b660edcb3e23b41efa1351f03f6b6791612c9) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit c77bd0c405077760b7dbfe620168bbe2e7cbbf1b) https://invent.kde.org/qt/qt/qtbase/-/commit/7edb2c33057c0e2bf01691726bf2c6c87e901d69 Git commit e4dbbcb42398cdc003432abcb6791f4633774ad8 by Qt Cherry-pick Bot (on behalf of Jean-Michaël Celerier) on 04/08/2026 at 03:14.. Add missing QStringList include in removed_api.cpp It was necessary due to the QStringList return in one of the old APIs. Change-Id: Ie2025e016bfb4bc6a52d7ae16b1a1e64792d66cf Reviewed-by: Thiago Macieira <[email protected]> (cherry picked from commit 59b2fd0a4fa768abd8723b9826a7ac69c98fe4cf) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit db406557ae5ac393bd700f552214d950a4801bd8) https://invent.kde.org/qt/qt/qtbase/-/commit/e4dbbcb42398cdc003432abcb6791f4633774ad8 Git commit f9af7540cd60a17c1cae233d7c3447a041e463bb by Qt Cherry-pick Bot (on behalf of Frédéric Lefebvre) on 04/08/2026 at 07:09.. Unblacklist tst_QScreen::grabWindow on windows tst_QScreen::grabWindow is no longer flaking or failing on windows. Task-number: QTBUG-100412 Pick-to: 6.8 Change-Id: I994536bae9151ad4260f64293b41b02a04b8c813 Reviewed-by: Mitch Curtis <[email protected]> (cherry picked from commit ad90ed7ba8497c0b4a7e2c67f73d97a480d46853) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit a134e206b6bbc56ff31eea0215a2ce0ebd3096ef) https://invent.kde.org/qt/qt/qtbase/-/commit/f9af7540cd60a17c1cae233d7c3447a041e463bb Git commit fd354aa0e694c68f54b8c7749e4ec11843fb59f4 by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Use the live modifier state during drag and drop The NSDraggingDestination callbacks hand us an id<NSDraggingInfo>, which carries no keyboard modifier state, so we reached for NSApp.currentEvent to fill in the modifiers of the QWSI drag events. But when the drag originates in another process the target process doesn't get any events at all, leaving us with whatever unrelated event happened to be current. We now read NSEvent.modifierFlags instead, mirroring what we already do for the buttons on the adjacent line via currentlyPressedMouseButtons(). That's also the semantics we want: the user can press Option mid-drag to switch between copy and move, and the drag feedback should follow the current state, not that of the initiating press. Pick-to: 6.8 Change-Id: I4ec86585c26a324e9e909949573885cb954062e7 Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit eab8f8afb059b2489022ea9c13e7aedd6b8b5138) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit a077a3a64c4d5d25e178e0c211ba4f5b776fc352) https://invent.kde.org/qt/qt/qtbase/-/commit/fd354aa0e694c68f54b8c7749e4ec11843fb59f4 Git commit 29594395884b1d021863beb8f50c75dab297fc6b by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Add privacy manifest for QtGui use of NSProcessInfo.systemUptime Per https://developer.apple.com/documentation/bundleresources/privacy-manifest-files Pick-to: 6.8 Change-Id: I5e2777684563bc7066b1be1790acd9f7dedd6c40 Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit a67383e2e95f9da40335a8b519a9a64382b70b47) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 607a2e489d516b2bbf38d003f948d62bf0cb3232) https://invent.kde.org/qt/qt/qtbase/-/commit/29594395884b1d021863beb8f50c75dab297fc6b Git commit 3273ee5d61ebbc94b958144cea664eb67d352cef by Qt Cherry-pick Bot (on behalf of Laszlo Agocs) on 04/08/2026 at 07:53.. gui/opengl: Add security consideration sections to docs Task-number: QTBUG-148739 Pick-to: 6.8 Change-Id: I2bf28ba35c38d7774c2fdca085fc2fbe165f64e0 Reviewed-by: Andy Nichols <[email protected]> (cherry picked from commit 249ea8ee9e59ce2cc9341be566ada4f1d39ce32f) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 5b5bfbc914071b1b3c50b4ef57247842df4b4a63) https://invent.kde.org/qt/qt/qtbase/-/commit/3273ee5d61ebbc94b958144cea664eb67d352cef Git commit 2785022cece98879a344bde622f02dc766b7a036 by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Don't rely on NSApp.currentEvent when starting a system move QPlatformWindow::startSystemMove() carries no event, so we reached for NSApp.currentEvent to get one to hand to performWindowDragWithEvent:. That is not reliable: as of macOS 27 a gesture recognizer can defer an action callback past the event that triggered it, and the call may not originate from a mouse event in the first place. We now synthesize the event we pass along, which is what AppKit itself does in this situation, and use the current button state to decide whether a window drag is possible at all. AppKit tracks the left mouse button for the duration of the drag, so unless it is actually pressed the call would do nothing. Reporting that up front is more accurate than the old event type switch, which also claimed success for right and other button presses. Pick-to: 6.8 Change-Id: Ie8f9f55dac64210695b7555a4819246a0191a822 Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit 9b342ddf2a8010e50c2bcc330967077479fa862a) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 5cd3007f4e0b5dd0e530e9d637b7ecee2330d7fa) https://invent.kde.org/qt/qt/qtbase/-/commit/2785022cece98879a344bde622f02dc766b7a036 Git commit eb3a13741d7f55e56b62c9d999acd1f40fa0becf by Qt Cherry-pick Bot (on behalf of Jean-Michaël Celerier) on 04/08/2026 at 07:53.. qversiontagging: don't emit ELF symbol versions in static builds A static build has no version script, so the version nodes referenced by the .symver directives are never defined and lld rejects them. Change-Id: I78cf8390fd724af89a6d8b3168bcd89f969e91c6 Reviewed-by: Thiago Macieira <[email protected]> (cherry picked from commit ae66214369fe9bc760aca4c525b5e5ec57c90f35) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 6c2a70b19b59583052270c10c89a70c5a2a0a177) https://invent.kde.org/qt/qt/qtbase/-/commit/eb3a13741d7f55e56b62c9d999acd1f40fa0becf Git commit 6fb0f33192a61fac9b54fb9d694e807038759c97 by Qt Cherry-pick Bot (on behalf of Jean-Michaël Celerier) on 04/08/2026 at 07:53.. BrotliCommon was not being linked to in static build Change-Id: Ie55fcb0160547f90450138945bec146529b5d3c4 Reviewed-by: Mårten Nordheim <[email protected]> (cherry picked from commit 0e25e784273c598d3a24dceee73e3aecb0b146b9) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 97ada28950b5e964981a36834385ef3b2397b292) https://invent.kde.org/qt/qt/qtbase/-/commit/6fb0f33192a61fac9b54fb9d694e807038759c97 Git commit 5ffacee8b9c0c79125e22b6dea19b325c1f36fda by Qt Cherry-pick Bot (on behalf of Jean-Michaël Celerier) on 04/08/2026 at 07:53.. QTipLabel: guard styleSheetParentDestroyed() definition Its declaration and the styleSheetParent member are already guarded by QT_CONFIG(style_stylesheet). Change-Id: Id9e73e1529d8433a48ca6d41ec5b6a9ac50f426d Reviewed-by: David Edmundson <[email protected]> Reviewed-by: Tim Blechmann <[email protected]> (cherry picked from commit 230d9f54483a207f51201fea73333f03aab0daeb) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 6c975573b29e9ef215b9f1d6678f8f34d4f6e7af) https://invent.kde.org/qt/qt/qtbase/-/commit/5ffacee8b9c0c79125e22b6dea19b325c1f36fda Git commit c17d458f173ab8b0371f9f5556e9ec21eea7edc7 by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Don't rely on NSApp.currentEvent when inserting newlines When the input method asks us to insert a newline we base the resulting key event on the key event we are currently interpreting, and only fall back to NSApp.currentEvent when we do not have one. That fallback is not reliable, as the current event may be unrelated to the text insertion, or missing altogether. The only things we need from the event in this situation are the timestamp and the modifiers, both of which are available as current state, so we now teach KeyEvent to fall back to that when constructed without an event. NSProcessInfo.processInfo.systemUptime shares its timebase with NSEvent.timestamp, so the resulting timestamps are still comparable to those of real events. Pick-to: 6.8 Change-Id: I823f52ae5002f27a42e47d0b2ea06b5db5674bcf Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit 08058688a9fa72262b43a479a3a7a53d93165226) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 85c3adf7d3b3e36e90230b24a93d3d94ad3cbd45) https://invent.kde.org/qt/qt/qtbase/-/commit/c17d458f173ab8b0371f9f5556e9ec21eea7edc7 Git commit ff6d3ba1787b2756f7d707efdfaccd7472227ade by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Don't rely on NSApp.currentEvent when inserting text To decide whether the input method merely echoed the key press, or transformed it into something else, we compare the inserted text to the characters of the key event. We were reaching for NSApp.currentEvent to get hold of that event, but the current event may well be unrelated to the text insertion. We now use the key event we are currently interpreting, which we already keep track of. For the cases where the text insertion does not originate from a key event at all, such as the Keyboard Viewer or an accent popup, we do not have one, and will then correctly conclude that the text does not match, and send it as an input method event. The event type check is no longer needed, as the interpreted key event is always a key press. This restores the state based approach that 294e4c7aa8cacd63c01d3836ce06c1f2d8c5ad5c replaced with the current event, but without a dedicated member for it. Pick-to: 6.8 Change-Id: I22d8bedd8a09135afaa25d6334f9b34ea29e8842 Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit f567bd1f79f9ab03b58dc1d732e8070c6dee7b53) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 112efca14714d25ac56e4beedde8a43232d612de) https://invent.kde.org/qt/qt/qtbase/-/commit/ff6d3ba1787b2756f7d707efdfaccd7472227ade Git commit 23289c1be0cb1d5c371e5cdbff282f6c3185223d by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Make the isMouseEvent helper available to the whole plugin It was a file static in qnswindow.mm, but we need the same check in other places as well. We now express it in terms of the existing cocoaEvent2QtMouseEvent, which as a side effect also covers the NSEventTypeOtherMouse* events that the file static left out, so frame strut handling and popup redirection now treat the middle mouse button like the left and right ones. Pick-to: 6.8 Change-Id: I244d962fcc52b0bbb43ec66a2860ee55a752d2ce Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit fd22838f0efb997da3462c225538508e603e201f) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 5d6ed915ec7630951fd4c480ec69ab5b94b817b7) https://invent.kde.org/qt/qt/qtbase/-/commit/23289c1be0cb1d5c371e5cdbff282f6c3185223d Git commit 6192d9edd00caa14ed6b67c32c0cd8cfe95cf815 by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 04/08/2026 at 07:53.. macOS: Don't assume the current event is a mouse event in the tray icon The status item button's action callback has no event parameter, so we consult NSApp.currentEvent to determine the activation reason. As of macOS 27 NSControls are driven by gesture recognizers, which defers the action callback past the event that triggered it, so the current event is not necessarily a mouse event anymore, and asking a non-mouse event for its clickCount raises an exception. We now report the activation as Unknown in that situation. Determining the real activation reason without an event is a larger task, as nothing but an event carries the click count. Pick-to: 6.8 Change-Id: I48b082fcd0778c22eec71c4c96c22b812ec9fc6d Reviewed-by: Doris Verria <[email protected]> (cherry picked from commit 65020b43cdd2c923c42ac4bc894c967ac90a0477) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit cd418b4b1a0c2ffc0ce5d1b708879e7fd3ec5a3f) https://invent.kde.org/qt/qt/qtbase/-/commit/6192d9edd00caa14ed6b67c32c0cd8cfe95cf815