JDK-7185280 : Jre7cert: focusgained does not get called for all focus req when do alt + tab
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-07-19
  • Updated: 2014-11-19
  • Resolved: 2012-11-06
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 JDK 8
7u10Fixed 8Fixed
Related Reports
Relates :  
JDK-8002362 - Build fails after integration of 7185280 to jdk7u-dev
Description
SHORT SUMMARY:

The problem is, when we alt+tab back to the new form, the focus does exist on
the default element, which is the first tf, but if we click on a different tf
in the same form, the text in that tf is not highlighted, though the cursor
moves to that tf. They claim this to be a side effect of the fact that forms
has missed receiving a FOCUS GAINED event whenever the issue reproduces.

INDICATORS: 7u6

COUNTER INDICATORS:  JDK 6

TRIGGERS: EBS/Forms App (ver?)

KNOWN WORKAROUND: Unclear

PRESENT SINCE: JDK 7 GA

HOW TO VERIFY: Forms Test case within bugdb

NOTES FOR SE: Not avail.

REGRESSION: TBD
Comments
Correct, but for any critical request SQE need to approve and so we need that in the bug before the approval can be completed. At the moment this fix is essentially "approved pending SQE approval" and so once we have that we can get it in. Ideally we need that today so that we can get the fix into the first build. Given the timing we may have to assume approval as there have clearly been emails around this issue with SQE
01-10-2012
just following up with awt team to see if SQE approved this. If so - we'll mark as 7u10-critical-approved.
01-10-2012
EVALUATION In order to proceed further with this issue, it is requried for the fix for 6981400 to have been pushed into 7u8. Anton is working on it.
27-08-2012
SUGGESTED FIX The correct fix for 6458497 is the fix for 6981400, which isn't in 7u-dev repo yet. So, the game plan is following: land the fix for 6981400 in 7u-dev, then back out the fix for 6458497, thus fixing this CR.
20-08-2012
SUGGESTED FIX Back out the problematic fix for 6458497 and fix it differently.
16-08-2012
EVALUATION This is a regression from 6458497.
16-08-2012