Bug 59099

Summary: http/tests/security/contentSecurityPolicy/frame-src-blocked.html causes the next test (image-allowed.html) to fail on Windows
Product: WebKit Reporter: Adam Roben (:aroben) <aroben>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, eric
Priority: P2 Keywords: LayoutTestFailure, PlatformOnly
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   
URL: http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r84485%20(11946)/http/tests/security/contentSecurityPolicy/image-allowed-pretty-diff.html

Description Adam Roben (:aroben) 2011-04-21 06:38:10 PDT 
http/tests/security/contentSecurityPolicy/image-allowed.html has been failing on Windows since r84460. Here's the diff:

@@ -1,2 +1,6 @@
+CONSOLE MESSAGE: line 1: Refused to load frame from 'http://127.0.0.1:8000/security/contentSecurityPolicy/resources/alert-fail.html' because of Content-Security-Policy.
+
+CONSOLE MESSAGE: line 1: Refused to load frame from 'http://127.0.0.1:8000/security/contentSecurityPolicy/resources/alert-fail.html' because of Content-Security-Policy.
+
 ALERT: PASS

Those console messages are actually from the previous test, iframe-src-blocked.html. I'm not sure how they're bleeding into this test. (Clearly those lines of output are appearing twice; once in the previous test, and once in this test.)
Comment 1 Adam Roben (:aroben) 2011-04-21 06:47:34 PDT 
Skipped frame-src-blocked.html in r84491.
Comment 3 Adam Barth 2011-04-21 09:10:20 PDT 
I think there's a problem with the patch.  It's logging to the console too much.  I'm going to partially revert it.
Comment 4 Adam Barth 2011-04-21 09:19:41 PDT 
I've removed the implementation of this feature, so the test now fails and shouldn't generate any console messages.  Sorry for the disruption.

http://trac.webkit.org/changeset/84506