https://bugs.kde.org/show_bug.cgi?id=523600

TraceyC <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
      Version First|master                      |6.7.80
        Reported In|                            |
                 CC|                            |[email protected]
     Ever confirmed|0                           |1

--- Comment #1 from TraceyC <[email protected]> ---
Thanks for the bug report, and the details, those are useful. I'm able to
reproduce this on both Plasma 6.7.3 and built from git-master using the
clipboard manager

I can confirm there doesn't appear to be a way to get at the confirmation pop
up, and a user not expecting it would think Plasma was just broken at this
point
Also, it's not possible to unpin or resize the clipboard pop up to get to the
confirmation behind it
Some of plasmashell remains functional, for instance the app menu pops up when
pressing Meta, but you can't get it to pop up by clicking on it
It's possible to click on applications shown behind the clipboard, they remain
responsive

Note:
When testing, to restore the yes/no prompt if you've chosen to never show it
again, remove these lines in ~/.config/plasmashellrc and restart plasmashell

klipperClearHistoryAskAgain=false
klipperClearHistoryStarredChoice=false
klipperRemoveStarredItemAskAgain=false

It's also necessary to make the clipboard widget rather large to get it to
overlap the dialog. At the default sizes, even on my laptop screen, the dialog
appears next to the widget. This doesn't negate the bug. The confirmation
absolutely should appear on the topmost layer (like a password prompt)

Funnily enough, I had an email notification that helpfully is on the topmost
layer and moves in response to other things on the screen. Maybe the
confirmation dialog could use similar patterns.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to