[Webkit-unassigned] [Bug 35052] New: When using showModalDialog, new dialog isn't modal until click fires

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 17 13:04:49 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=35052

           Summary: When using showModalDialog, new dialog isn't modal
                    until click fires
           Product: WebKit
           Version: 525.x (Safari 3.2)
          Platform: PC
        OS/Version: Windows XP
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joyannefoster at yahoo.com


If you launch a new dialog with showModalDialog in Safari 4.0.4, the new dialog
isn't truly modal until you click on it or the parent.  The effect is, you can
click on something on the parent window 1 time.  Additionally, you have to
click on the child window 2 times to get it to respond.  The first click seems
to click on the parent window (in the background) as if it was clicked behind
the dialog.

To test:
Open a simple HTML page (code below)
Click on the test button 1 time
Allow modal dialog to popup.
Now, highlight the dfdfdf text on the parent dialog.
Notice that once you release the mouse button, you can't un-highlight or do
anything else to the parent until the child is closed.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>eSite Builder - Host Window</title>
<script type="text/javascript">
function doTest()
{   
    window.showModalDialog("/test.html",null,"dialogHeight: 444px; dialogWidth:
444px; edge: Raised; center: Yes; resizable: No; help: No; status: No;");
}

</script>
</head>
<body >
<form>
<input type="button" value="test" onclick="doTest();"
style="position:absolute;left:333px;top:200px;background-color:red;">
dfdfdf
</form>
</body>
</html>

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list