| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Unset-mouseGrabberPopup-if-it-s-removed-from-childre.patch | [PATCH] Unset mouseGrabberPopup if it's removed from children The mouseGrabberPopup is supposed to be unset in handleRelease, however when the exit transition of the mouseGrabberPopup (that closed itself on button press) finishes before the release event is delivered, it unparents itself from the overlay (see QQuickPopupPrivate::finalizeExitTransition) and the overlay sets itself invisible if there is nothing else visible in it. Because the overlay is not visible it handles no events anymore and the release is missed and the grabber is never unset. When opening another non-modal popup the overlay then will continue forwarding the events to now invisible popup. So when the overlay loses the currently grabbing popup as a child we need to reset mouseGrabberPopup. (adapted from commit d07ee1345acd8100fa5cbb7f05c0aaf5f87f4cae) (cherry picked from commit 1a59ef4218658ffc476909ef4fca13d6cf86d04b) |
David Redondo <qt@david-redondo.de> | no | 2021-07-19 | ||
| 0002-Ensure-we-don-t-crash-when-changing-sizes-after-clea.patch | [PATCH] Ensure we don't crash when changing sizes after cleanup This addresses the problems I've seen during destruction. Only encountered it when using complex layouts on a DialogButtonBox. (cherry picked from commit 8b24d2bf1655e8491bdd74013579e09cd009e8fc in qtdeclarative) |
Aleix Pol <aleixpol@kde.org> | no | 2022-01-04 | ||
| 0003-QQuickAction-don-t-grab-the-same-shortcut-multiple-t.patch | [PATCH] QQuickAction: don't grab the same shortcut multiple times If the entry for the QQuickItem that the QQuickAction is set on has already grabbed the shortcut, then m_shortcutId is no longer 0 and we must not overwrite the value. Otherwise, the QQuickItem removing itself from the action might not remove the correct entry from Qt's shortcut map, leaving a dangling pointer behind. Multiple calls to QQuickActionPrivate::ShortcutEntry::grab are possible, because we grab the shortcut whenever the shortcut changes, or when an item representing the action becomes visible. The test case added reproduces this scenario by adding the action to a menu item and then making the menu explicitly visible, resulting in two calls to grab() which should be idempotent. (cherry picked from commit 45af5ef2f63704adc515e29260ad8c6aaf51f08e in qtdeclarative) |
Oliver Eftevaag <oliver.eftevaag@qt.io> | no | 2022-01-19 | ||
| 0004-QQuickAbstractButton-fix-crash-on-destruction.patch | [PATCH] QQuickAbstractButton: fix crash on destruction If we listen for size changes we also need to remove the object listened to when it's deleted. (cherry picked from commit 720ffaeb60d43123522066e1de3a69ad551644aa in qtdeclarative) |
Ulf Hermann <ulf.hermann@qt.io> | no | 2022-01-11 | ||
| 0006-Fix-scroll-bars-not-showing-up-when-binding-to-stand.patch | [PATCH] Fix scroll bars not showing up when binding to standalone contentItem 908aa77d16e00f2bccc0ddae0f8b61955c56a6a1 hid old scroll bars, but didn't account for the situation where the old scroll bars would be put back into place, and so they never showed up. In the case of the linked bug report, since there was a binding to the ScrollView's contentItem, a default Flickable would be created. After that binding was evaluated, the contentItem was set, causing the scroll bars to be hidden (as part of the process of disconnecting from the old flickable). To fix the issue, we now do the reverse of hideOldItem when a new contentItem is set. (cherry picked from qtdeclarative 58bae53237417f28eac6d772fa6ecab657f8a73f) |
Mitch Curtis <mitch.curtis@qt.io> | no | 2022-07-18 | ||
| 0007-implement-a11y-pressing-of-qquickabstractbutton.patch | [PATCH] implement a11y pressing of qquickabstractbutton this adds a pressAction default implementation that simply calls trigger (which in turn either triggers the action or emits a click), allowing accessibility tools to issue a button press via a11y api. (cherry picked from commit 705659eaaf47af72eeb5f5c742e18a5c665a76eb in qtdeclarative) |
Harald Sitter <sitter@kde.org> | no | 2022-11-02 | ||
| 0008-Fix-the-popup-position-of-a-Menu.patch | [PATCH] Fix the popup position of a Menu QPA code should operate in native coord. Treat QWidgetPlatformMenu::showPopup's input as native coord. (cherry picked from commit f8cf17166c9af147f0b8fea72f5b4a8a6098a5d7 in qtdeclarative) |
Inho Lee <inho.lee@qt.io> | no | 2022-08-22 | ||
| disable_fontless_examples_build.patch | disable examples using fontello fonts. There are two examples using the embedded fontello font. As the fonts is not in it's preferred form of modification we needed to remove them. Also the fonts are not letters, so they can not be replaced with another one. . So we disable the build of this to examples. |
Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> | not-needed | debian |