JDK-8129550 : "java.awt.Window.setAlwaysOnTop" doesn't work from the applet loaded with Classic Java Plugin
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u95
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • Submitted: 2015-06-23
  • Updated: 2016-04-29
  • Resolved: 2016-04-29
Related Reports
Blocks :  
JDK-8141628 - Classic Java Plugin does not function in IE starting from JDK 6u101
Blocks :  
JDK-8146102 - Applet, IE are frozen after the applet loaded with Classic Java Plugin shows modal dialog
Duplicate :  
JDK-8146102 - Applet, IE are frozen after the applet loaded with Classic Java Plugin shows modal dialog
Description
FULL PRODUCT VERSION :
JDK 6u95 b12

ADDITIONAL OS VERSION INFORMATION :
MS Windows 7 OS

A DESCRIPTION OF THE PROBLEM :
When an applet loaded in Internet Explorer (IE) 9 with Classic Java Plugin from JRE 6 shows "javax.swing.JFrame" instance on which the method "java.awt.Window.setAlwaysOnTop" was called, the shown frame window is positioned correctly on top of all windows on the desktop. However, after the applet shows JavaScript "alert" modal dialog via LiveConnect call and after the applet shows Java modal dialog, for which the frame is specified as a parent, from a parallel thread, then after closing of the described two modal dialogs, IE 9 window can be put on top of JFrame instance. This result is incorrect from the view point of the user, since "java.awt.Window.setAlwaysOnTop" method was called on the instance of JFrame.

WORKAROUNDS :
Load the applet with next-generation Java Plug-in, however the user cannot use this workaround.
Comments
Closing the bug as a duplicate of JDK-8146102.
29-04-2016
Additional testing showed that in IE 9, where JDK-8146102 cannot be reproduced, the issue is reproducible using the user's test case with JRE 6u115 b12, and cannot be reproduced with a custom build of JRE 6 compiled from the source code of JRE 6u115 b12 to which the fix for JDK-8146102 was added. Based on this test result and analogous information from the user specified in the previous comment, it can be concluded that: - this issue is resolved by the fix for JDK-8146102. - this issue can be closed as a duplicate of JDK-8146102.
26-04-2016
The issue could not be reproduced by means of the user's test case on MS Windows 7 OS in IE 11 with JRE 6u101, JRE 6u95, because presence of 2 additional bugs did not allow to reach the final steps in the user's test scenario. The following 2 bugs blocking the work on this issue were filed: 1. JDK-8141628 2. JDK-8146102 The issue could not be reproduced in IE 11 with JRE 6 compiled from the latest development source code with the fixes for the specified above 2 blocking issues. The user was provided with the custom build of JRE 6u113 compiled with these 2 additional fixes (JDK-8141628, JDK-8146102). The user confirmed that the issue is not reproducible in the user's environment with this custom build of JRE 6u113.
26-04-2016