Bug 435061

Summary: No minimum or maximum width and not enough padding
Product: [Plasma] plasmashell Reporter: Felipe Kinoshita <kinofhek>
Component: Clipboard widget & pop-upAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: med.medin.2014, nate, noahadvs
Priority: NOR Keywords: usability
Version First Reported In: 5.21.3   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: first video
second video
image

Description Felipe Kinoshita 2021-03-28 12:11:05 UTC
Created attachment 137127 [details]
first video

Some problems with Klipper pop-up

STEPS TO REPRODUCE
1. Launch Klipper pop-up (you'll probably need to assign a keyboard shortcut to "Open Klipper at mouse position") 

OBSERVED RESULT
When copying some large text Klippler don't line break occupying one third of my screen. (first attached video)

It's really hard to distinguish between different clipboard content, more spacing/margin and more contrasting color could help. (attached image)

If you launch Klipper with an empty clipboard, window title is cut. (second attached video)

EXPECTED RESULT
Klipper should have a maximum width so when clipboard content is too large it doesn't occupy a big portion of the screen.

Klipper should space and make different clipboard contents easier to read.

Klipper pop-up should have a minimum width so window title is not cut.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Felipe Kinoshita 2021-03-28 12:11:25 UTC
Created attachment 137128 [details]
second video
Comment 2 Felipe Kinoshita 2021-03-28 12:12:12 UTC
Created attachment 137129 [details]
image
Comment 3 Nate Graham 2021-04-01 18:49:53 UTC
All good ideas.
Comment 4 Nate Graham 2021-04-01 21:19:05 UTC
*** Bug 429192 has been marked as a duplicate of this bug. ***
Comment 5 Noah Davis 2023-08-11 20:22:08 UTC
This appears to be fixed. Tested with Plasma 5.27.7