https://bugs.kde.org/show_bug.cgi?id=495536
Niccolò Venerandi <nicc...@venerandi.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Latest Commit| |https://invent.kde.org/plas
| |ma/kwin/-/commit/975276ef5b
| |8aced9883460a1d296958437760
| |c0a
Resolution|--- |FIXED
--- Comment #3 from Niccolò Venerandi <nicc...@venerandi.com> ---
Git commit 975276ef5b8aced9883460a1d296958437760c0a by Niccolò Venerandi.
Committed on 01/12/2024 at 17:22.
Pushed by niccolove into branch 'master'.
Simplify Keys forwarding in Overview
Previously, the search bar and the window heap would forward the keypresses
to each other. The new version has just one forwarding statement, in the
root item, that specifies the exact forwarding order (heap, searchbar,
search results).
According to Keys QML documentation, the order of handling of events is
the following:
* Item- specific key handling, e.g. TextInput key handling
* Items specified in forwardTo
* specific key handlers, e.g. onReturnPressed
* onPressed, onReleased handlers
* parent item
When we type and then press arrow keys, the focus goes to the heap. When we
again press an arrow key, the `forwardTo` is handled before the `onPressed`
handler of the heap, and the heap has a `forwardTo` to the search box, which
accepts the event and moves the cursor within the input box.
By only having one forward to which clearly defines the order of handling we
avoid that.
M +1 -4 src/plugins/overview/qml/main.qml
https://invent.kde.org/plasma/kwin/-/commit/975276ef5b8aced9883460a1d296958437760c0a
--
You are receiving this mail because:
You are watching all bug changes.
