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 116890 - Using BMiddle or BRight shouldn't select?
Using BMiddle or BRight shouldn't select?
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other All
: Normal normal
: Need diagnosis
Assigned To: gtk-bugs
gtk-bugs
: 132924 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-07-07 15:25 UTC by Calum Benson
Modified: 2013-02-11 05:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Calum Benson 2003-07-07 15:25:04 UTC
From a Sun beta tester:

"In GNOME, users can perform a select action using BLeft or one of the
other pointing device buttons.  For example, clicking BLeft,  BMiddle (or
the wheel), or BRight on a list item (e.g., in a list box, combo box,
drop-down combo box) selects the item, and clicking BLeft, BMiddle (or the
wheel), or BRight on a pull-down menu title opens the menu.  A select
action should be performed using only BLeft.

Users have come to expect that BMiddle and BRight will have no effect if
they inadvertently use these buttons while working in an application.  If
these buttons are active, the possibility of inadvertently choosing an
incorrect action is increased, with the possibility of significant negative
consequences in the kinds of mission-critical applications that I deal
with.  I would expect that other user communities would share these concerns."
Comment 1 Owen Taylor 2003-08-01 18:51:00 UTC
So, what's your opinion, then?
Comment 2 Calum Benson 2003-08-05 17:48:24 UTC
Well, the only example of this that's caught me out personally (quite
a few times!) is right-clicking on an Actions menu item, only to find
out it activates the item rather than popping up another menu like the
Applications menu does.  That's arguably the fault of the Applications
menu for giving me that expectation, but until that changes it's an
expectation a lot of people seem to have.  (And Windows users will
come armed with it too, since they can right-click on Start menu items
to do stuff).

I think that's probably the main thing that has the potential to do
actual damage... people right-clicking things to see if they have a
context menu, only to find out they've clicked a button or something
instead.  The other instances do still have potential to contribute to
a broken mental model though... e.g. "I can activate a scroll button
or a spin button with button3 but not a combo box button, yet they all
look pretty much the same".
Comment 3 Owen Taylor 2003-08-11 18:43:39 UTC
* It would be useful to have a comprehensive places that
  need to be fixed.

* In some cases, other button clicks have particular meaning -
  button3 on a spinbutton arrow or scrollbutton arrow 
  means "go to the end", button 2 anywhere on a scrolllbar
  means "jump to position" (a particularly useful one.)

  These probably shouldn't be changed.
Comment 4 Owen Taylor 2004-01-30 17:26:21 UTC
*** Bug 132924 has been marked as a duplicate of this bug. ***
Comment 5 Matthias Clasen 2004-03-10 09:45:30 UTC
No "comprehensive list of places" to restrict to left button has 
appeared yet.
Comment 6 Mantas Kriaučiūnas 2004-08-12 15:19:30 UTC
I also think, that left, right and middle mouse button clicks should produce
different behaviour in menu or other gtk+ widgets.
Comment 7 Matthias Clasen 2013-02-11 05:13:15 UTC
closing old bugs