JDK-6973199 : java/awt/Robot/RobotWheelTest/RobotWheelTest.html failed on JDK7 b102 bug passed on b101
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: linux
  • CPU: generic
  • Submitted: 2010-07-29
  • Updated: 2011-03-07
  • Resolved: 2011-03-07
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.
JDK 7
7 b116Fixed
Related Reports
Relates :  
JDK-6957166 - With XAWT, set arguments properly creating a MouseWheelEvent.
Relates :  
JDK-7045623 - closed/java/awt/Robot/RobotWheelTest/RobotWheelTest.html failed again on JDK7 since b134
Description
see comments
Comments
EVALUATION The 6957166 tiny fix was not necessary in regard to -number of requests on it -native behavior (windows and linux desktops don't use such 'acceleration') -incompatibility it introduces (works on linux only) -addon for other platforms -increased testing complexity(?)
13-10-2010
EVALUATION The behaviour on windows and linux obviously differs and fixing this would introduce if-else into the test which is bad. Or we should change Windows behavious as well.
01-10-2010
EVALUATION Since the fix for 6957166 we started to respect the clickCount value calculated inside the awt machinery for every MouseEvent type. We used to ignore it until jdk7b102. Now we have a bit different behaviour under Linux and Windows. On Linux we respect clickCount, on Windows we basically ignore it. Indeed we use some winapi metrics to determine the line number to scroll but in most cases we use constant value of 1. So technically we can do the same under Windows as well but there are zero requests about it in the database. This new behaviour is pretty much suitable for large images, webserfing, etc. Whether we treat it as a defect in JDK or in the test itself, in both cases I consider this failure as a minor bug. But would we find other use cases that make big pain we will roll this fix back.
10-09-2010
EVALUATION Caused by the change for 6957166. Since that we use clickCount as the number of wheelevents.
19-08-2010