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

Side by Side Diff: LayoutTests/imported/web-platform-tests/html/dom/documents/dom-tree-accessors/nameditem-03-expected.txt

Issue 1291723004: Remove all support for <applet> handling in Chrome. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Rebase Created 5 years, 3 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
(Empty)
1 This is a testharness.js-based test.
2 FAIL If there is one applet, it should be returned (name) assert_equals: expecte d (string) "test1" but got (undefined) undefined
3 FAIL If there are two applets, a collection should be returned. (name) assert_eq uals: expected (string) "test2" but got (undefined) undefined
4 FAIL If there is one applet, it should be returned (id) assert_true: "test3" in document should be true expected true got false
5 FAIL If there are two applets, a collection should be returned. (id) assert_true : "test4" in document should be true expected true got false
6 FAIL If there are two applets, a collection should be returned. (name and id) as sert_equals: expected (string) "test5" but got (undefined) undefined
7 FAIL If there are two applets, a collection should be returned. (id and name) as sert_equals: expected (string) "test6" but got (undefined) undefined
8 FAIL A name shouldn't affect getting an applet by id assert_true: "test7" in doc ument should be true expected true got false
9 FAIL An id shouldn't affect getting an applet by name assert_equals: expected (s tring) "test8" but got (undefined) undefined
10 Harness: the test ran to completion.
11
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698