Index: LayoutTests/http/tests/security/sandboxed-iframe-modify-self-expected.txt |
diff --git a/LayoutTests/http/tests/security/sandboxed-iframe-modify-self-expected.txt b/LayoutTests/http/tests/security/sandboxed-iframe-modify-self-expected.txt |
index 601ee0800a3a559f6e1411d238911f3ca4c45c48..995be78e25d25faf86525c6ab8a03220f993517e 100644 |
--- a/LayoutTests/http/tests/security/sandboxed-iframe-modify-self-expected.txt |
+++ b/LayoutTests/http/tests/security/sandboxed-iframe-modify-self-expected.txt |
@@ -1,4 +1,4 @@ |
-CONSOLE MESSAGE: Sandbox access violation: Blocked a frame at "http://127.0.0.1:8000" from accessing a frame at "http://127.0.0.1:8000". The frame requesting access is sandboxed and lacks the "allow-same-origin" flag. |
+CONSOLE MESSAGE: line 9: Uncaught SecurityError: Sandbox access violation: Blocked a frame at "http://127.0.0.1:8000" from accessing a frame at "http://127.0.0.1:8000". The frame requesting access is sandboxed and lacks the "allow-same-origin" flag. |
This is a "sanity" test case to verify that a sandboxed frame cannot break out of its sandbox by modifying its own sandbox attribute. Two attempts are made: |
First, an attempt is made to modify the sandbox attribute of the "self" object, referring to the frame's window. This should not have any effect (the attribute is associated with the iframe DOM node, not the window). No warning is expected. |