After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756961 - Don't select a menu entry only by releasing right mouse button
Don't select a menu entry only by releasing right mouse button
Status: RESOLVED NOTABUG
Product: gtk+
Classification: Platform
Component: Widget: GtkMenu
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-10-22 12:23 UTC by Jan Niklas Hasse (Account disabled)
Modified: 2017-02-09 23:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jan Niklas Hasse (Account disabled) 2015-10-22 12:23:17 UTC
On Linux you can press the right mouse button to open the context menu, hold it, move the mouse over to a menu entry, and then release the right mouse button to select the entry.

This doesn't work on OS X or Windows, so for the sake of consistency I vote for disabling this behaviour by default.

This would finally fix #591258. Although this bug report has the status "RESOLVED FIXED", it's still an issue for many people (me including).
Comment 1 timppis 2015-10-22 15:00:21 UTC
In my opinion would be a pretty bad kind of "fix" to an issue that could/should be fixed in another way (just doing what Qt or many others do, yet still retaining the hold-clicking feature).

> This doesn't work on OS X or Windows, so for the sake of consistency I vote for disabling this behaviour by default.

That's a dangerous route. What other unique and useful features should be dropped for the sake of such consistency?
Comment 2 Matthias Clasen 2015-10-22 15:22:37 UTC
not a bug, but a feature, as far as I'm concerned.
Comment 3 Jan Niklas Hasse (Account disabled) 2015-10-22 15:46:45 UTC
(In reply to timppis from comment #1)
> In my opinion would be a pretty bad kind of "fix" to an issue that
> could/should be fixed in another way (just doing what Qt or many others do,
> yet still retaining the hold-clicking feature).

How about disabling this and ONLY re-enable it when this better fix is ready. And no, adding 5 px padding is NOT a fix, see for example https://bugzilla.gnome.org/show_bug.cgi?id=591258#c28

> That's a dangerous route. What other unique and useful features should be
> dropped for the sake of such consistency?

I disagree strongly that this feature is useful.

And even it was a useful feature, it should still be dropped if it causes bugs like this: https://www.youtube.com/watch?v=SuLsWRHTViQ

It's just not worth it.

(In reply to Matthias Clasen from comment #2)
> not a bug, but a feature, as far as I'm concerned.

How do I report feature request for Gtk+?
Comment 4 Matthias Clasen 2015-10-22 16:39:23 UTC
(In reply to Jan Niklas Hasse from comment #3)

> (In reply to Matthias Clasen from comment #2)
> > not a bug, but a feature, as far as I'm concerned.
> 
> How do I report feature request for Gtk+?

You may have misunderstood. The thing you complain about is a feature, and I won't remove it, even if you don't like it.
Comment 5 Jan Niklas Hasse (Account disabled) 2015-10-22 16:49:47 UTC
(In reply to Matthias Clasen from comment #4)
> (In reply to Jan Niklas Hasse from comment #3)
> 
> > (In reply to Matthias Clasen from comment #2)
> > > not a bug, but a feature, as far as I'm concerned.
> > 
> > How do I report feature request for Gtk+?
> 
> You may have misunderstood. The thing you complain about is a feature, and I
> won't remove it, even if you don't like it.

What about the ability to turn this feature off?

I don't want it to be turned off because I don't like it. I want it to be turned off because it's causing bugs.
Comment 6 Robert Andrew 2017-02-09 23:19:09 UTC
I am not sure I got it right. In my case, the hold-click feature "works" when the attachment can be opened in the message body (after a left-click on the attachment button, see bug #778220) but otherwise not. To be clearer, the behavior is not predictable: sometimes only the hold-click will work (and thus prevent the user from choosing the right option if they were expecting a second click to select the option), sometimes both hold-click and click-click will work. Is that a feature or a bug?

Thanks.

PS: I do not expect hold-and-click in the case of a button. Hold-and-click and click-twice can perfectly be combined to suit most user preferences, but the behavior has to be predictable.