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.)
Skipped frame-src-blocked.html in r84491.
Similar problem on Qt: http://build.webkit.org/results/Qt%20Linux%20Release/r84499%20(31763)/http/tests/security/contentSecurityPolicy/image-allowed-pretty-diff.html
I think there's a problem with the patch. It's logging to the console too much. I'm going to partially revert it.
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