JDK-2129524 : All editable fields get frozen.
  • Type: Backport
  • Backport of: JDK-6291992
  • Component: client-libs
  • Sub-Component: java.awt
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2005-09-06
  • Updated: 2006-07-25
  • Resolved: 2005-11-26
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.
Other JDK 6
5.0u10Fixed 6 b62Fixed
Comments
EVALUATION The regression test fails due to the following reasons: - the test was written incorrectly - Windows: the test used ActionListener to show a dialog, however there is a problem with ActionEvent time. It appears that the time recorded by EventQueue while ActionEvent is processed can sometimes be newer than the time of ActionEvent. As the result, type-ahead doesn't queue the necessary key events. This happens because ActionEvent is dispatched using InvocationEvent from WButtonPeer - Dual-opteron: in the type-ahead code we have checks which enqueue key events and drop markers which use strong comparision operators "<" and ">". However, due to the fast CPU, ActionEvent, KeyEvents, and FocusEvent may appear to all have the same time. Which will mean that KeyEvents won't be enqueued or FocusEvent won't remove marker We work on fixing this issues for Mustang, as part of the fix for 5064013. Until all of them are fixed, the regression test for this fix will fail and this bug will be considered in progress.
03-11-2005
EVALUATION It has been noticed that regression test for this bug is still failing on AMD64/DualOpteron platform. We don't have such a platform though.
27-09-2005
EVALUATION Several reasons were found for this and related bugs: - EventQueue.setCurrentEventAndMostRecentTimeImpl method may set the time from the earlier event then the current time. - Dialog.show could start enqueuing key events after it has already received focus resulting in all key events being delayed until the next focus transfer - KeyboardFocusManager.shouldNativelyFocusHeavyweight was accessing important global fields without synchronization from several places, resulting in usage of different values in those places - DefaultKeyboardFocusManager.dispatchEvent was skipping focus events arriving with the target equal to the current focus owner but wasn't removing associated type-ahead markers All this bugs have been fixed in Mustang. The fix will be backported to 5.0u (supposedly u7).
07-09-2005