JDK-6624085 : Fourth mouse button (wheel) is treated like second button - isPopupTrigger returns true
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: x86
  • Submitted: 2007-10-31
  • Updated: 2015-06-04
  • Resolved: 2014-08-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u40Fixed 9 b32Fixed
Related Reports
Relates :  
This is bug originally reported against NetBeans, for details please see

It seems that on systems with special trackball, isPopupTrigger returns true in situations where it should not.
HW description - trackball with three buttons and a fourth button that
makes the mouse/trackball scroll instead of move the pointer, i.e. holding that
button transforms the trackball wheel into a scroll wheel (really nifty).

Scrolling with fourth button pressed works okay, but after maybe half a second it pops up a context menu, as if the second mouse button was pressed, which wasn't.

I'm attaching small test application. Original reporter (added to interest list) confirms that problem can be reproduced 100% on his trackball with this test app.

I'll ask original reporter to add detail info about his trackball HW and java version...

EVALUATION Currently there is almost no support for multi-buttons mice and other special devices like trackballs in AWT. Umbrella RFE for this is 6315717.

EVALUATION Reassigned to AWT