Created attachment 174319 [details] Video showing the issue with the context menu showing up during resize. *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Using Meta+Mouse will send the mouse event down to the window it is being manipulated on. For example, using Meta+LeftMouse to move a Dolphin window will initiate a file drag and move the window at the same time, or using Meta+RightMouse on a Dolphin window will open the context menu while resizing the window. STEPS TO REPRODUCE 1. Have Meta+RightClick as "Resize" 2. Using it on a GTK Windows (such as Firefox) -- notice that the window does not receive a right-click event 3. Use that on a Qt window (such as Dolphin) -- notice that the window receives the right-click event (eg. opens the context menu) OBSERVED RESULT On Qt windows (such as Dolphin) resizing using Meta+RightClick causes the context menu to open, while on non-Qt (such as Firefox or Thunar) it does not. EXPECTED RESULT The mouse event not to be passed along to the window if the Meta key is held and window is being resized. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 6800HS with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon 680M ADDITIONAL INFORMATION Added a video attachment showing the issue, with Dolphin (on the left) and Thunar (on the right). Both windows I am resizing using Meta+Right Click. As it is shown, Dolphin's context menu pops up, while on Thunar it does not. I feel like this is a regression, as I firmly believe this behaviour would have driven me insane.
Apologies, seems it was a qt6-base upstream issue, that had been fixed just recently. In Arch Linux, updating qt6-base from 6.7.3-1 to 6.7.3-2 had fixed this issue.