[Webkit-unassigned] [Bug 50106] New: Asynchronous policy check in WebKit2 changes the codeflow in WebCore

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Nov 26 04:12:33 PST 2010


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

           Summary: Asynchronous policy check in WebKit2 changes the
                    codeflow in WebCore
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P3
         Component: WebKit2
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: zbujtas at gmail.com


with the following code

var newWin = window.open("", "awin");
newWin.document.open();
newWin.document.close();

in WebKit2, the document.open() cancels the outstanding policy check, issued by window.open(), while with WebKit, since the policy check happens in a sync manner, document.open() does not cancel it. When the execution hits document.open() (Document::open(Document* ownerDocument)), with WebKit2 the frame is in FrameStateProvisional state, while with WebKit, it is in FrameStateComplete state.

-- 
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