Bug 378247 - Applet doesn't close after selecting a clipboad entry with enter
Summary: Applet doesn't close after selecting a clipboad entry with enter
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard (show other bugs)
Version: 5.15.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Martin Flöser
URL:
Keywords:
: 343519 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-03-29 17:35 UTC by Robin Appelman
Modified: 2021-08-07 20:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.23
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Appelman 2017-03-29 17:35:05 UTC 
After navigating to a clipboard entry from the applet and selecting it with <enter> the applet menu stays open, requiring the user to close it manually using <esc>.

This makes using the applet with the keyboard more annoying than it could be, which is a shame since the applet works much nicer than the "show at mouse location" otherwise.

Reproducible: Always

Steps to Reproduce:
1) open tray menu
2) select an item in the clipboard history
3) press enter

Actual Results:  
item is selected, applet stays open

Expected Results:  
select element and close the applet
Comment 1 Sudhir Khanger 2018-09-12 03:42:58 UTC 
This is a huge usability issue. The behavior of the clipboard manager is not consistent post-selection between mouse-click and enter key. If I press mouse-click on an item, it is selected and the widget is closed. If I press enter key then the item is selected and nothing is done to the widget. Now I first have to Esc to reach the un-filtered clipboard manager and then press Esc again.
Comment 2 Patrick Silva 2019-03-01 16:17:18 UTC 
This usability problem persists.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.2
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1
Comment 3 Nate Graham 2021-04-01 20:07:38 UTC 
*** Bug 343519 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2021-08-07 20:00:05 UTC 
This works now.