Bug 458569

Summary: Search should always select the first entry if the mouse is not moved
Product: [Plasma] plasmashell Reporter: Enrico <enricobe>
Component: Application Launcher (Kickoff)Assignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: mikel5764, nate, noahadvs
Priority: NOR    
Version: 5.25.4   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screen capture of the wrong behavior

Description Enrico 2022-08-31 19:08:01 UTC
Created attachment 151740 [details]
Screen capture of the wrong behavior

SUMMARY
***
Hello,
I think that KickOff has a wrong behavior if the mouse is moved and then you search something. After any search it should select the first entry of the search, so you can open the search result by pressing RETURN.
Now KickOff selects the entry *where the mouse cursor is placed* and not the first result of the search.

***
STEPS TO REPRODUCE
1. Open KickOff
2. Move the mouse cursor on any part of the opened menu 
3. Start a search

OBSERVED RESULT
KickOff selects the entry where the mouse cursor is placed and not the first entry of the search, which is supposed to be the most relevant.

EXPECTED RESULT
After a search KickOff should always select the first entry of the search results. It should select another entry only if the mouse is moved *after* the search and not only because the mouse is left in any part of the KickOff search results list.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.15.0-46-generic (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
See the attachment. As you can see, I searched "MPV" and I expect KickOff to open MPV when I press "Return", because it's the first result.
Instead it opens other search results only because the mouse was placed here *before* starting the search.
Comment 1 Nate Graham 2022-08-31 20:50:34 UTC

*** This bug has been marked as a duplicate of bug 454349 ***