Bug 408845 - Clicking on separator closes context menu
Summary: Clicking on separator closes context menu
Status: RESOLVED UPSTREAM
Alias: None
Product: Breeze
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-17 18:46 UTC by guimarcalsilva
Modified: 2019-06-21 08:57 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description guimarcalsilva 2019-06-17 18:46:32 UTC
SUMMARY


STEPS TO REPRODUCE
1. Right click in any KDE software to open a context menu
2. Click on a separator

OBSERVED RESULT

Context menu gets closed

EXPECTED RESULT

It should stay open

ADDITIONAL INFORMATION

I think this behavior should be changed because:

1. This is inconsistent: Context menus on GTK apps like Firefox don't show the same behavior.

2. A user can accidentally click on a separator instead of clicking on the desired option. Since the context menu closes, it can make the user think he clicked on the right place when he actually didn't.

Example: The option "Cut" and the separator are next to each other. 
A user may try to click on the "Cut" option on Dolphin to move a file > He accidentally clicks on the separator and don't notice > When going to another folder to paste the file he notices the paste option is not showing up.

This can create a lot of usability problems, especially for users in a hurry, with poor mouse skills, a bad vision or users using trackpads.

Thanks.


SOFTWARE/OS VERSIONS
KDE neon Unstable Edition
KDE Plasma: 5.16.80
KDE Frameworks: 5.60.0
Qt: 5.12.3
Kernel: 4.18.0-21-generic 64 bits
CPU: 2 × Intel® Core™ i5-6200U CPU @ 2.30GHz
3,9 GiB RAM
Comment 1 Hugo Pereira Da Costa 2019-06-21 03:11:20 UTC
This is a valid issue/concern, however this is not a breeze bug. Happens with any widget style. In fact, mouse event handling is not done (in general) by the style, but upstream, by Qt. 
Issue should be reported and possibly fixed there. 
In principle, this could also be addressed in the style itself, but that would only be a hack, that should then be duplicated to any widget style.
Not the right way to go.
Comment 2 Nate Graham 2019-06-21 08:57:21 UTC
Makes sense, thanks Hugo!

Please report this to Qt using https://bugreports.qt.io/. Thanks!