Bug 396708

Summary: It's easy to accidentally select a context menu item when you accidentally right-click
Product: [Plasma] Breeze Reporter: jon2kx
Component: QStyleAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: minor CC: nate
Priority: NOR Keywords: accessibility, usability
Version: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
URL: https://bugreports.qt.io/browse/QTBUG-57849
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description jon2kx 2018-07-20 19:43:41 UTC
On the upper 60-70% of the screen, the context menu expands from the left, and down. While on the lower remaining 40-30% of the screen, it expands from the left and up.

Even if you hold the right click for a tiny amount of time, which is the most common thing, the menu pops up. The threshold is like two pixels to the right and it is selected. So by the time your brain has told your finger to release, if there was any motion from the right, and you release it while an option in the context menu has popped up, it treats that click as a select as well.That whole process happens in like 1/16th of second, before you can register what just happened.

The first option from the bottom when using most applications, close. What prompted me to report this issue Konsole: the first option from the bottom is close tab.

Cannot find any option to turn this behavior off. I really don't want my right click to select anything.
Comment 1 Nate Graham 2018-07-20 20:53:57 UTC
If I'm understanding you properly, the issue is that when you accidentally right-click your mouse and move the cursor a few pixels, it's too easy to accidentally select a menu item, with potentially unwanted consequences. Is that right?

If so, this might be something we can solve in Breeze by changing where the context menu pops up, or by adding a little bit of padding somewhere. In macOS for example, this is handled by giving menus a little bit of top and bottom padding to increase the number of pixels that the cursor has to travel before it's underneath a menu item.
Comment 2 Christoph Feck 2018-07-21 00:34:40 UTC
The actual bug is https://bugreports.qt.io/browse/QTBUG-57849, but adding a workaround in all styles is also an option. </s>
Comment 3 jon2kx 2018-07-21 03:11:18 UTC
That would be agreeable, although it would be nice to have the option to disable right click and select, but I suspect that it would affect a great many little things, or take a lot more to implement. Like swatting a fly with a mallet.

I am in agreement with you.
Comment 4 Nate Graham 2018-07-23 02:17:12 UTC
Christoph is right, let's track this upstream.
Comment 5 Laura David Hurka 2020-04-24 11:50:48 UTC
It doesn’t appear that upstream resoled this bug in the last 2 years. And today, at least on my system, right-click instantly triggers the first menu entry even without any mouse movement.

It happens only with Breeze style, not with MS Windows 9x style, which has padding arround the menu.

What should we do? Wait longer to do it semantically correct, or change the padding in Breeze to actually mitigate the problem?
Comment 6 Nate Graham 2020-04-24 18:27:42 UTC
Working around it in Breeze by adding a little bit of top madding could technically be considered a stylistic change that just happens to also fix this bug, so yeah, it's probably not terribly unreasonable.

As for the Qt bug, I don't think we can count on it to get get randomly fixed one day. a KDE person will probably have to submit a patch.
Comment 7 Nate Graham 2020-04-24 18:27:51 UTC
s/madding/padding/
Comment 8 Nate Graham 2021-02-16 21:06:17 UTC

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