JDK-6210088 : The fix for 4774166 need to be changed
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux_suse_sles_8.2,windows_xp
  • CPU: x86
  • Submitted: 2004-12-17
  • Updated: 2011-01-31
  • Resolved: 2005-02-12
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.0u4Fixed 6 b24Fixed
Related Reports
Relates :  
JDK-4774166 - InputVerifier not called after a window loses then regains focus
Relates :  
JDK-6382144 - REGRESSION: InputVerifier and JOptionPane
Description
The fix for 4774166 need to be changed to work correctly with several keyboard focus managers. We need to create InputVerifierKeyboardFocusListener per focus manager.
###@###.### 2004-12-17 16:45:41 GMT
Comments
EVALUATION It's possible to use static private package AWT method KeyboardFocusManager.getMostRecentFocusOwner(Window window) to fix 4774166. This is simpler than previous idea of the fix for 4774166 - using property change listener and WeakHashMap to store last focus owners for windows, that are about to lose focus. Also, this solution solves the problem with using different keyboard focus managers. ###@###.### 2005-1-19 17:47:26 GMT
17-12-2004
SUGGESTED FIX http://sa.sfbay.sun.com/projects/swing_data/mustang/6210088.2 ###@###.### 2005-1-19 17:47:26 GMT
17-12-2004