Bug 59099 - http/tests/security/contentSecurityPolicy/frame-src-blocked.html causes the next test (image-allowed.html) to fail on Windows
Summary: http/tests/security/contentSecurityPolicy/frame-src-blocked.html causes the n...
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Nobody
URL: http://build.webkit.org/results/Windo...
Keywords: LayoutTestFailure, PlatformOnly
Depends on:
Reported: 2011-04-21 06:38 PDT by Adam Roben (:aroben)
Modified: 2011-04-21 09:19 PDT (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
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 '' because of Content-Security-Policy.
+CONSOLE MESSAGE: line 1: Refused to load frame from '' because of Content-Security-Policy.

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.