Index: LayoutTests/fast/frames/sandboxed-iframe-history-denied-expected.txt |
diff --git a/LayoutTests/fast/frames/sandboxed-iframe-history-denied-expected.txt b/LayoutTests/fast/frames/sandboxed-iframe-history-denied-expected.txt |
index a763dcb58d408304ca86697b5bca86bb4e52f5f5..dfd3db81efc92007cd83791cbee0bdd11ef700af 100644 |
--- a/LayoutTests/fast/frames/sandboxed-iframe-history-denied-expected.txt |
+++ b/LayoutTests/fast/frames/sandboxed-iframe-history-denied-expected.txt |
@@ -1,6 +1,4 @@ |
-CONSOLE MESSAGE: Unsafe JavaScript attempt to initiate navigation for frame with URL 'script>'. The frame attempting navigation of the top-level window is sandboxed, but the 'allow-top-navigation' flag is not set. |
- |
-ALERT: PASS |
-This test verifies that a sandboxed IFrame cannot navigate the top-level frame using the history API. |
+CONSOLE MESSAGE: Sandbox access violation: Blocked a frame at "null" from accessing a frame at "". The frame requesting access is sandboxed and lacks the "allow-same-origin" flag. |
eseidel
2013/05/01 04:17:23
Seems like a rather lacking message. :)
Use mkwst_at_chromium.org plz.
2013/05/01 04:45:19
Yeah. The message isn't wrong, but it's certainly
|
+This test verifies that a sandboxed IFrame cannot access the history object of the top-level frame. It passes if a console error is present, noting that the inner frame cannot access the outer. |