Tested OS/browser:
- Windows XP-pro(sp2)/ IE 6
 -Windows Vista (32 bit- enabled UAC)- business/ IE 7
                
Tested builds: (used both new plug-in and old plug-in)
- jre 6u10-b09 (promoted build)
- deployment nightly build of 01/07/2008:
(/java/deployment/nightly/1.6.0_10/nightly/2008-01-07/windows-i586/jre-6u10-fcs-bin-b411-windows-i586-p-07_jan_2008.exe)
               
Problem: The focused windows stays behind another windows if using the new plug-in.
If switching to use the old plug-in on the same machine, same test scenario, the focus windows is on the top and that's the expected behaviour.

Steps to reproduce:
------------------
1) Enable the show console option
2) Using browser to load the following page:
http://jsqalab.sfbay/results/sqenfs-1/export1/comp/stt/st2/jpi2/tc501/TC05-01_Top.html
[Note: if using the new plug-in, you have to bring the main windows back on top of java console in order to proceed to step #3]
3) Click 'New Window' button
4) Expect a new browser windows to be open (and have the focus) on the top of the main browser windows


Here are problems with the focus if using the new plug-in:
A) The main browser windows (open after step #2) is located behind the Java console which has the focus (reserved order to occur if using the old plug-in)
B) The new browser windows (open after step #3) has the focus but stays behind the main browser windows (reserved order to occur if using the old plug-in)

On the side note, this test case can also be used to reproduce the crash in CR# 6648457 (if you do this sequence a couple of times: close the window browser open in step #4 and repeat step #3)