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

Side by Side Diff: LayoutTests/imported/web-platform-tests/html/browsers/the-window-object/window-named-properties-expected.txt

Issue 1121703002: bindings: Uses V8's named property interceptor for Window. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Updated a test result. Created 5 years, 4 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 | Annotate | Revision Log
OLDNEW
1 This is a testharness.js-based test. 1 This is a testharness.js-based test.
2 PASS Static name 2 PASS Static name
3 FAIL Static name on the prototype assert_false: Window.prototype.hasOwnProperty( "bar") expected false got true 3 FAIL Static name on the prototype assert_false: Window.prototype.hasOwnProperty( "bar") expected false got true
4 FAIL constructor assert_equals: expected (function) function "function Window() { [native code] }" but got (object) object "[object Window]" 4 FAIL constructor assert_equals: expected false but got true
haraken 2015/08/25 07:04:52 Just to confirm: This FAIL line is expected, right
Yuki 2015/08/25 08:03:52 Yes, it's caused because we don't have WindowPrope
5 PASS Dynamic name 5 PASS Dynamic name
6 PASS Ghost name 6 PASS Ghost name
7 Harness: the test ran to completion. 7 Harness: the test ran to completion.
8 8
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698