https://bugs.kde.org/show_bug.cgi?id=449533
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|master |5.23.90
CC| |noaha...@gmail.com
Priority|HI |VHI
--- Comment #4 from Nate Graham <n...@kde.org> ---
Git bisect says this was caused by the following commit:
d58b9eabf3959473030c685690277d9d2f03f388 is the first bad commit
commit d58b9eabf3959473030c685690277d9d2f03f388
Author: Noah Davis <noaha...@gmail.com>
Date: Mon Jan 31 09:21:50 2022 -0500
systemtray AbstractItem: Improve touch feedback
Applets in PlasmoidItem were blocking events from reaching the
ToolTipArea, so I moved the on hover logic to the AbstractItem's
MouseArea and put the MouseArea over the iconContainer. The
iconContainer is the parent of applets. Presses tend to hit the center,
which is where the applet is, preventing ToolTipArea::containsMouse from
being true and preventing the highlight from moving to the pressed item.
Hopefully this doesn't cause duplicate actions when events reach the
applet. I tested the patch on the nightcolor applet and all the other
default applets and didn't see anything wrong. I think this may be
because the signals are sending QML MouseEvents to the applets, causing
them to be accepted if the applet can accept them. Then when the signal
handlers are done, since the events are already accepted, they should
not move beyond the MouseArea and cause another round of event handling.
.../package/contents/ui/items/AbstractItem.qml | 24 +++++++++++++---------
1 file changed, 14 insertions(+), 10 deletions(-)
That commit made it into the stable branch which just got tarred today. Raising
to VHI priority as this is a serious regression we shouldn't ship with.
--
You are receiving this mail because:
You are watching all bug changes.
