SUMMARY Context menus that are shown by right-clicking on the list of processes are persistent, i.e. don't close when the user clicks on the window decoration or other windows or desktop. This behavior is inconsistent with context menus created by other applications. STEPS TO REPRODUCE 1. Open System Monitor on the process list tab. 2. Right-click on one of the processes. In the context menu, hover mouse over "Send Signal". 3. Without clicking on the context menu, move the mouse away and click on the window decoration, another application window or desktop. OBSERVED RESULT The context menu stays open. EXPECTED RESULT The context menu should disappear. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-50-lowlatency (64-bit) Graphics Platform: X11 Processors: 16 × 12th Gen Intel® Core™ i7-12700K Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
This is a limitation of QtQuick Controls 2 menus and needs to be fixed in Qt.
(In reply to Arjen Hiemstra from comment #1) > This is a limitation of QtQuick Controls 2 menus and needs to be fixed in Qt. Then please report this to Qt and post a link here. I won't be able to provide any details to Qt devs wrt. where the problem is and what needs to be done.
I'm going to reopen this so that it doesn't get lost. Feel free to close it if you report the problem to Qt (please post a link to it as well).
As a side note, I don't quite understand why System Monitor has to use some different API for displaying context menus, which behaves differently from every other application on the system. This breaks UX. Why not use the "normal" context menus?
The upstream bug is https://bugreports.qt.io/browse/QTBUG-69558 > As a side note, I don't quite understand why System Monitor has to use some different API for displaying context menus, which behaves differently from every other application on the system. This breaks UX. Why not use the "normal" context menus? It's not a different API, most QtQuick applications will use these same APIs. The difference is between QtWidgets and QtQuick. And choosing between those two has little to do with what menu style is used - the advantages of QtQuick greatly outweigh the minor annoyance of an in-application menu.