Bug 396951

Summary: Clipboard widget scrolls down on display and mouse enter
Product: [Applications] klipper Reporter: aib <aibok42>
Component: plasma-widgetAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, kde, kde, nate, plasma-bugs
Priority: NOR    
Version: 5.12.6   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description aib 2018-07-29 10:02:55 UTC
First of all, either there is no proper place to report bugs about the Clipboard widget, or it's impossible to find. (I assume Klipper is something else, as Clipboard doesn't use Klipper's klipperrc)

Anyway, this is fairly straightforward: Left clicking on the scissors icon to open up the Clipboard widget causes the clipboard history contents to come into view scrolled down, about 2 ticks from the top. Putting the mouse cursor over the said contents causes another 2 ticks of scrolling.

Given that the top 3-5 entries are the ones the user is almost always interested in accessing, this is a very annoying bug.
Comment 1 Patrick Silva 2018-07-29 23:24:41 UTC
bug 391646 is related.
Device notifier applet has this same annoying usability problem.
Comment 2 David Edmundson 2018-08-02 23:18:04 UTC
What scissors icon?
Comment 3 aib 2018-08-02 23:26:29 UTC
The icon I use to access the clipboard history widget; though from Dr. Chapatin's report it might as well be any scrollable taskbar widget['s icon].

What am I doing wrong that I'm unable to find the proper subsystem for the bug report, as well as being unclear about the icons I use?
Comment 4 David Edmundson 2018-08-02 23:30:03 UTC
do you have a different theme? I have a little clipboard icon
Comment 5 Kai Uwe Broulik 2018-08-03 06:26:09 UTC
In Air and Oxygen it's a scissors icon
Comment 6 aib 2018-08-03 07:43:37 UTC
Ah, yes, big fan of Oxygen Dark here

Sorry for talking in terms of icons, I'm still not clear about the widget's official name :)
Comment 7 Nate Graham 2021-04-01 19:22:43 UTC

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