JDK-8159886 : Window of a newly launched Oracle Forms applet loses focus
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 8u74
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2016-06-20
  • Updated: 2019-05-29
  • Resolved: 2018-11-29
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.
Related Reports
Relates :  
AWT frame window shown by Oracle Forms applet during its loading suddenly in Z-order becomes positioned behind Internet Explorer (IE) 11 window with a web page containing the applet, after the applet loading is finished. The issue is not reproducible with JRE 7 and JRE 6.

The bug can be reproduced only with the user's web site which uses Oracle Forms applet. After too many attempts to create a minimal test case which did not let to guarantee that Java Plug-in native code flow will be the same as during loading of the minimal test case with the code flow during loading of the user's applet, it was decided to stop wasting any more time on creation of the test case for this sophisticated scenario.
This seems to be a bug in the deployment/plugin component which was never open sourced. Removing redhat-interest.

A minimal test case was attached to the bug record as "AppletFrameIsMovedBehindBrowser.zip" file. On 03/14/2018 the user provided with access to the web site with the applet allowing to reproduce the issue. It was discovered that 2 different applets are involved in the test scenario on the user's web site and that The class of the 2nd applet, whose window is finally moved behind the browser window, is a derivative of the class "java.applet.Applet" and its window is a derivative of the class "java.awt.Frame". Based on the discovered information, a new minimal test case "AppletFrameIsMovedBehindBrowser.zip" was created, this variant of the test case fails on JDK 8 containing the fix for JDK-8136759 and does not fail on JDK 8 without this fix. This issue is a regression of JDK-8136759 and a continuation of the following sequence of fixes: JDK-8056915 --caused--> JDK-8080977 --caused--> (JDK-8133665, JDK-8136759 --caused--> this issue (JDK-8159886))

The user did not provide a test case, closing the bug with "Cannot Reproduce" resolution.

On 07/01/2016 the issue was reproduced using the user's test case on MS Windows 7 OS in IE 11 browser with JRE 8u91 b15. On 11/21/2016 the issue was reproduced with JDK 8 compiled from the latest version of development source code, JDK 8u72 b15 and the issue could not be reproduced with JDK 8u73 b02, JDK 8u71 b15. It was defined that this issue is caused by the fix for the bug JDK-8136759, because it was practically proven that reversion of the fix JDK-8136759 from JDK 8 latest version of development source code eliminates the issue. On 12/05/2017 it was found out that the URL of the user's applet became expired and inaccessible, the user asked for provision of the the new URL to the test case. On 01/22/2018 the user provided with a new URL, however the test case applet was still inaccessible and the user was informed about this on 01/31/2018. On 02/02/2018 I created a minimal test case, however soon it was found out that the test case failed with JREs with which the user's original test case had not fail. On 02/19/2018 after 2 weeks of unsuccessful attempts to create a test case which would have failed and passed with JREs same to the JREs with which the user's test case was registered to fail or pass, the user was informed that without a test case from the user it is not possible to confirm that this issue is a bug in JDK 8 and to continue to work on the issue, the user was informed that the bug would be closed with "Cannot Reproduce" resolution, if the test case is not provided.