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

Side by Side Diff: third_party/WebKit/LayoutTests/external/wpt/domparsing/createContextualFragment-expected.txt

Issue 2658793002: Report w3c test result count for WPT (Closed)
Patch Set: update Created 3 years, 10 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 This is a testharness.js-based test. 1 This is a testharness.js-based test.
2 Found 35 tests. 16 PASS 19 FAIL 0 TIMEOUT 0 NOTRUN
2 PASS Must not throw INVALID_STATE_ERR for a detached node. 3 PASS Must not throw INVALID_STATE_ERR for a detached node.
3 PASS Must throw TypeError when calling without arguments 4 PASS Must throw TypeError when calling without arguments
4 PASS Simple test with paragraphs 5 PASS Simple test with paragraphs
5 PASS Don't auto-create <body> when applied to <html> 6 PASS Don't auto-create <body> when applied to <html>
6 PASS <script>s should be run when appended to the document (but not before) 7 PASS <script>s should be run when appended to the document (but not before)
7 FAIL createContextualFragment should work even when the context is <area> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'are a', which is not supported. 8 FAIL createContextualFragment should work even when the context is <area> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'are a', which is not supported.
8 FAIL createContextualFragment should work even when the context is <base> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'bas e', which is not supported. 9 FAIL createContextualFragment should work even when the context is <base> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'bas e', which is not supported.
9 FAIL createContextualFragment should work even when the context is <basefont> Fa iled to execute 'createContextualFragment' on 'Range': The range's container is 'basefont', which is not supported. 10 FAIL createContextualFragment should work even when the context is <basefont> Fa iled to execute 'createContextualFragment' on 'Range': The range's container is 'basefont', which is not supported.
10 PASS createContextualFragment should work even when the context is <bgsound> 11 PASS createContextualFragment should work even when the context is <bgsound>
11 FAIL createContextualFragment should work even when the context is <br> Failed t o execute 'createContextualFragment' on 'Range': The range's container is 'br', which is not supported. 12 FAIL createContextualFragment should work even when the context is <br> Failed t o execute 'createContextualFragment' on 'Range': The range's container is 'br', which is not supported.
(...skipping 17 matching lines...) Expand all
29 PASS Implicit <body> creation 30 PASS Implicit <body> creation
30 PASS Namespace generally shouldn't matter 31 PASS Namespace generally shouldn't matter
31 PASS <html> in a different namespace shouldn't be special 32 PASS <html> in a different namespace shouldn't be special
32 PASS SVG namespace shouldn't be special 33 PASS SVG namespace shouldn't be special
33 PASS null should be stringified 34 PASS null should be stringified
34 PASS undefined should be stringified 35 PASS undefined should be stringified
35 PASS Text nodes shouldn't be special 36 PASS Text nodes shouldn't be special
36 PASS Non-Element parent should not be special 37 PASS Non-Element parent should not be special
37 Harness: the test ran to completion. 38 Harness: the test ran to completion.
38 39
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698