Bug 50106

Summary:

WebKit2 asynchronous policy check for window.open() clashes with synchronous operations on the opened window's DOM

Product:

WebKit

Reporter:

alan <zalan>

Component:

WebKit2

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED WORKSFORME

Severity:

Normal

CC:

andersca, ap, sam

Priority:

Version:

528+ (Nightly build)

Hardware:

All

OS:

All

Attachments:

Description	Flags
test case	none

alan

Reported 2010-11-26 04:12:33 PST

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.

Attachments
test case (697 bytes, text/html) 2010-11-26 04:20 PST, alan	no flags	Details
View All Add attachment proposed patch, testcase, etc.

alan

Comment 1 2010-11-26 04:20:30 PST

Created attachment 74916 [details] test case

alan

Comment 2 2010-11-29 01:30:19 PST

got fixed with https://bugs.webkit.org/show_bug.cgi?id=49605 Committed r72122: http://trac.webkit.org/changeset/72122

Note You need to log in before you can comment on or make changes to this bug.