Index: third_party/WebKit/LayoutTests/fast/dom/Window/timeout-callback-scope-expected.txt |
diff --git a/third_party/WebKit/LayoutTests/fast/dom/Window/timeout-callback-scope-expected.txt b/third_party/WebKit/LayoutTests/fast/dom/Window/timeout-callback-scope-expected.txt |
index 484ad6cc8b85bb7121b666230cda3b00898e56b7..7d036912226f6013d38aa433a973c64253669bea 100644 |
--- a/third_party/WebKit/LayoutTests/fast/dom/Window/timeout-callback-scope-expected.txt |
+++ b/third_party/WebKit/LayoutTests/fast/dom/Window/timeout-callback-scope-expected.txt |
@@ -1,4 +1,5 @@ |
-Test verifies that a timeout callback is run in the proper execution context. 2 timeouts are set on a child iframe's window. 'Closure' callback should execute in the main page, 'string' callback should execute in the iframe. Test passes if you see 2 lines 'PASS' below. |
+Test verifies that a timeout callback is run in the proper execution context. 3 timeouts are set on a child iframe's window. Test passes if you see 3 lines 'PASS' below. See also: https://html.spec.whatwg.org/multipage/webappapis.html#timer-initialisation-steps |
-PASS |
-PASS |
+PASS -- function argument: if the argument is a function, then the callback function must run in the relevant realm for that function object. |
+PASS -- string argument: if the argument is a string, then it must be compiled in the relevant realm for the context object, hence must run in the relevant realm for the context object. |
+PASS -- callback this value: the callback this value must be the context object. |