| Index: third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt
|
| diff --git a/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt b/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt
|
| index 3b01534569af873f8dd8240a5604decb006c0c3f..656a79f6b4d38c357097d3ac5263840a1c0c5a68 100644
|
| --- a/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt
|
| +++ b/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt
|
| @@ -1,5 +1,5 @@
|
| CONSOLE ERROR: line 24: Refused to frame 'https://localhost:8443/security/contentSecurityPolicy/resources/alert-fail.html' because it violates the following Content Security Policy directive: "frame-src 'self' http://localhost:8080".
|
| -
|
| +CONSOLE ERROR: line 24:
|
| ALERT: PASS
|
| ALERT: PASS
|
| IFrames blocked by CSP should generate a 'load' event, regardless of blocked state. This means they appear to be normal cross-origin loads, thereby not leaking URL information directly to JS.
|
|
|