JDK-6689088 : Focus traversal doesn't work in the reverse order / related to the SR 70175950 / CR 6684528
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 5.0u15
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2008-04-15
  • Updated: 2011-02-16
  • Resolved: 2008-06-17
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 Other
5.0u16-rev b03Fixed 5.0u17Fixed
Related Reports
Relates :  
JDK-6386592 - REGRESSION: Frame doesn't get focus back when dialog become closed
Description
Verizon said, this issue is related to SR# 70175950. As per engineering comment, this is a bug in JDK which got fixed in jdk 7.0 but cu has requested the backport fix in jdk 1.5 update 15 and upper, on windows 2000 platform. The issue to be handled this case is "Focus traversal doesn't work in the reverse order". This is on Windows 2000 / JDK 1.5

Snippet from Kannan's email :

   The original issue ( SR 70175950 / CR 6684528 ) is definitely different from this one but the latter (new) one is a jdk bug. I discussed with PDE and this is a problem specific to Window object. The good news is that it  has been recently fixed in 7.0.  I can work on backporting the fix to 5.0 and other releases. So you may want to file another escalation for this issue.
Problem scenario:

- There is a Frame with a textfield containing the keyboard focus.
- On the press of Home key on the keyboard on the textfield, a popupmenu is shown. The popupmenu is a customized one using Window object.
- On disposing the popupmenu using Escape key, the focus is expected to get back to the textfield but the focus is lost and is seen nowhere.
Comments
EVALUATION Please check bug 6386592 which has been fixed in 6.0 and 7.0 and the scenario is a superset of this bug.
29-05-2008
EVALUATION Just a note that this is an issue only when a Window is popped up. If it was a Frame or a Dialog or its subclass, the focus would have been set back onto the textfield in the scenario provided in the Description.
29-05-2008
EVALUATION The fix is to synthesize the window activation on the parent frame. This sets the focus back onto the last focussed component in the parent frame.
15-05-2008