Bug 505068

Summary: Desktop widget enters edit mode when accessing Context menu
Product: [Plasma] plasmashell Reporter: ulterno
Component: NotificationsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cwo.kde, kde
Priority: NOR    
Version First Reported In: 6.3.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshots corresponding to reproduction steps

Description ulterno 2025-05-31 16:31:32 UTC
Created attachment 181938 [details]
Screenshots corresponding to reproduction steps

SUMMARY
In the Expanded Desktop Widget of Notifications, on activating the Actions context menu of a copied file (by dolphin), the desktop widget enters edit/resize mode after a small delay

STEPS TO REPRODUCE
0. Have an expanded Desktop widget for Notifications
1. Copy an ods file using Dolphin
2. In the actions for the Notification that comes up for the copied file, click on the button to open the context menu
3. Hover the mouse pointer over the opened menu for a second or so

OBSERVED RESULT
The widget enters edit/resize mode (not the whole desktop, but only that widget)

EXPECTED RESULT
No edit/resize mode is activated and I get to interact with the context menu

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.7-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 7600

ADDITIONAL INFORMATION

Unlike 416909 and 457979, this one does not require a long click (or even a right click)
PFA for step-by-step screenshots
Comment 1 cwo 2025-05-31 16:45:47 UTC
Can reproduce.
Comment 2 cwo 2025-06-01 08:05:08 UTC
This is a desktop containment issue, not immediately related to the Notification widget (though it could work around it by opening on click instead of press, but that's not really a solution).

Fixing bug 416909 generally requires more thinking, but I think we might be able to fix this particular case somewhat cleanly.

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