Bug 424459

Summary: Panel Configuration mode closes when dismissing the "undo removing this widget" notification
Product: [Plasma] plasmashell Reporter: postix <postix>
Component: Edit ModeAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: minor CC: cwo.kde, nate, niccolo, postix
Priority: NOR Keywords: usability
Version: 5.19.3   
Target Milestone: 1.0   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of the sticky notification

Description postix 2020-07-20 11:24:54 UTC
Created attachment 130280 [details]
Screenshot of the sticky notification

SUMMARY

The panel edit mode is very fragile. Clicking somewhere else will immediately close it, yet there's an explicit closing button for this purpose. I'd suggest to keep it open. 


STEPS TO REPRODUCE
1. Unlock widgtets
2. Edit panel
3. Remove a widget
4. Click away the sticky notification which overlays the panel edit

OBSERVED RESULT

The edit mode is exited

EXPECTED RESULT

The edit mode is kept open


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2020-07-23 19:14:56 UTC
I can confirm the bug that dismissing the undo notification exits panel edit mode.

Not sure whether we should fix just this, or make any click elsewhere not automatically exit panel edit mode. Personally I find it kind of convenient to be able to exit panel edit mode by clicking on the desktop, but I can see how this might seem unexpected
Comment 2 Christoph Feck 2020-08-17 19:29:08 UTC
Is bug 424712 a contradicting request?
Comment 3 cwo 2024-06-18 20:45:11 UTC
This is still an issue in current Plasma 6.1, except that with the new separation between Panel Configuration and Edit Mode, Edit Mode remains active and only the Panel Configuration closes when pressing the button. I'll take the liberty to update the Summary to reflect this.
Comment 4 Niccolò Venerandi 2024-10-02 20:02:29 UTC
It seems like this has been since fixed in master.