United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6239224 IE hangs when a modal dialog is active and the mouse is clicked on the browser
6239224 : IE hangs when a modal dialog is active and the mouse is clicked on the browser

Details
Type:
Bug
Submit Date:
2005-03-11
Status:
Resolved
Updated Date:
2010-12-07
Project Name:
JDK
Resolved Date:
2005-04-25
Component:
deploy
OS:
windows
Sub-Component:
plugin
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:
1.4.2_09

Related Reports
Backport:
JDK-2124496 - IE hangs when a modal dialog is active and the mouse is clicked on the browser
Backport:
JDK-2124524 - IE hangs when a modal dialog is active and the mouse is clicked on the browser
Relates:
JDK-6228734 - filechoser dialogue can not be controled by mouse in 1.4.2_07
Relates:
JDK-6247308 - REGRESSION: Particular Applets won't work in IE anymore when using the latest Java plugin

Sub Tasks

Description
The bug occurs right from 1.4.2_07, to 1.5 update release and all the way to mustang current build (b26 at this point).
The bug occurs when a modal dialog is popped up through an applet through a Javascript.

STEPS TO REPRODUCE:
- Compile Test.java and launch the attached applet (Test.html)
- Click on the html (not applet) "Read" button
- A filedialog pops up. Click anywhere on the browser (except the applet region). The browser hangs.

###@###.### 2005-03-11 01:57:20 GMT

Comments
EVALUATION

Problem: When an AWT modal dialog is popped up through Javascript(only) the browser window doesn't receive any windows messsages and hence hangs most of the times. In this bug, the modal dialog popped up is a FileDialog and doesn't receive any key/mouse events.
This regression is a side effect of fix for 5077565,5079850. The previous fix removed code for pumping messages to the browser window while a modal dialog is active and only user messages are dispatched.

Fix: The fix proposed here is to have different codepaths (one when a modal dialog is active and the other when it is not). The fix checks for the existence of the modal dialog in the do-while loop of JavaAdapter::WaitForJS(...) method. This has to be done because WaitForJS gets called before the modal dialog comes up and so GetActiveWindow will never point to the dialog unless put into the loop.
In summary,
       When modal dialog is active -> pump windows messages to the browser window
       When modal dialog is not present -> pump user messages (code that currently exists after fix for 5077565,5079850)


###@###.### 2005-03-23 19:40:07 GMT
2005-03-11


Hardware and Software, Engineered to Work Together