Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(23)

Side by Side Diff: third_party/WebKit/LayoutTests/fast/dom/Window/timeout-callback-scope-expected.txt

Issue 2049493005: binding: Uses the relevant realm instead of the current realm (1 of ?) (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Addressed a review comment. Created 4 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 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 i n the main page, 'string' callback should execute in the iframe. Test passes if you see 2 lines 'PASS' below. 1 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 'PAS S' below. See also: https://html.spec.whatwg.org/multipage/webappapis.html#timer -initialisation-steps
2 2
3 PASS 3 PASS -- function argument: if the argument is a function, then the callback func tion must run in the relevant realm for that function object.
4 PASS 4 PASS -- string argument: if the argument is a string, then it must be compiled i n the relevant realm for the context object, hence must run in the relevant real m for the context object.
5 PASS -- callback this value: the callback this value must be the context object.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698