Bug 39830 - [v8] Sandboxed Iframes with the allow-same-origin flag dosn't have a contentWindow attribute
Summary: [v8] Sandboxed Iframes with the allow-same-origin flag dosn't have a contentW...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 04:56 PDT by Robert Stopp
Modified: 2010-05-28 15:54 PDT (History)
1 user (show)

See Also:


Attachments
The testcase shows that the second iframe can't get designmode because it has no valid contentWindow pointer. (2.46 KB, text/html)
2010-05-28 14:22 PDT, Robert Stopp
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Stopp 2010-05-27 04:56:52 PDT
Don't know if this is a Webkit or a V8 bug. A chromium developer proposed the usage of sandboxed iframes for disabled scripting in designmode documents. Doing so with the attribute sandbox="allow-same-origin", which should give us the same result like in all other browsers with designmode iframes, the contentWindow reference is absent. Is this a bug or a feature?
Comment 1 Alexey Proskuryakov 2010-05-28 13:06:56 PDT
Could you please provide a test case or an URL of site where this problem occurs?
Comment 2 Robert Stopp 2010-05-28 14:22:10 PDT
Created attachment 57377 [details]
The testcase shows that the second iframe can't get designmode because it has no valid contentWindow pointer.
Comment 3 Alexey Proskuryakov 2010-05-28 14:37:13 PDT
I cannot reproduce this with r60144 nightly, looks like a v8 issue.
Comment 4 Robert Stopp 2010-05-28 15:47:54 PDT
After uninstalling/ reinstalling Safari the Webkit nightlys run on my PC.
And i can confirm it's a Chromium issue. The Webkit issue is the not disabled form-elements. Without "allow-forms" the form should not submit. 
Maybe i file a extra bug for this.