https://bugs.kde.org/show_bug.cgi?id=516923
cwo <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/plas | |ma/milou/-/commit/ff582f3be | |a99260bf63940907e7e4919f0e7 | |40e8 --- Comment #3 from cwo <[email protected]> --- Git commit ff582f3bea99260bf63940907e7e4919f0e740e8 by Christoph Wolk. Committed on 02/03/2026 at 10:54. Pushed by cwo into branch 'master'. lib/ResultsView: deselect first on Home/End ResultsView moves the currentIndex to the first/last result on Home/End press from the search field, if the cursor is already at the beginning/ end. This does not seem unreasonable, as the press would otherwise do nothing... but Home/End also clear the selection, so users may press it to clear the current selection so they can prepend/append something to the existing query. Currently, a user attempting to do so may move the currentIndex instead, in particular for prepending when reopening krunner: it will start with the existing query selected and the cursor at the beginning of the field. (appending has the same issue, but this situation is less common as it only happens after manually selecting). Instead, also check whether there is selected text, and let the SearchField handle it in that case even if the cursor is already at the beginning/end. Its handling of the key will clear the selection, so the next press will move the currentIndex, but the user has a chance to prepend/append first. FIXED-IN 6.7.0 M +2 -2 lib/ResultsView.qml https://invent.kde.org/plasma/milou/-/commit/ff582f3bea99260bf63940907e7e4919f0e740e8 -- You are receiving this mail because: You are watching all bug changes.
