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

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

Issue 2707973002: Remove blacklist on .innerHTML and .outerHTML (Closed)
Patch Set: Typo fix 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
« no previous file with comments | « no previous file | third_party/WebKit/LayoutTests/external/wpt/html/syntax/serializing-html-fragments/serializing-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 This is a testharness.js-based test.
2 PASS Must not throw INVALID_STATE_ERR for a detached node.
3 PASS Must throw TypeError when calling without arguments
4 PASS Simple test with paragraphs
5 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 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 <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 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 <col> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'col' , which is not supported.
13 FAIL createContextualFragment should work even when the context is <embed> Faile d to execute 'createContextualFragment' on 'Range': The range's container is 'em bed', which is not supported.
14 FAIL createContextualFragment should work even when the context is <frame> Faile d to execute 'createContextualFragment' on 'Range': The range's container is 'fr ame', which is not supported.
15 FAIL createContextualFragment should work even when the context is <hr> Failed t o execute 'createContextualFragment' on 'Range': The range's container is 'hr', which is not supported.
16 FAIL createContextualFragment should work even when the context is <img> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'img' , which is not supported.
17 FAIL createContextualFragment should work even when the context is <input> Faile d to execute 'createContextualFragment' on 'Range': The range's container is 'in put', which is not supported.
18 FAIL createContextualFragment should work even when the context is <keygen> Fail ed to execute 'createContextualFragment' on 'Range': The range's container is 'k eygen', which is not supported.
19 FAIL createContextualFragment should work even when the context is <link> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'lin k', which is not supported.
20 FAIL createContextualFragment should work even when the context is <meta> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'met a', which is not supported.
21 FAIL createContextualFragment should work even when the context is <param> Faile d to execute 'createContextualFragment' on 'Range': The range's container is 'pa ram', which is not supported.
22 FAIL createContextualFragment should work even when the context is <source> Fail ed to execute 'createContextualFragment' on 'Range': The range's container is 's ource', which is not supported.
23 FAIL createContextualFragment should work even when the context is <track> Faile d to execute 'createContextualFragment' on 'Range': The range's container is 'tr ack', which is not supported.
24 FAIL createContextualFragment should work even when the context is <wbr> Failed to execute 'createContextualFragment' on 'Range': The range's container is 'wbr' , which is not supported.
25 FAIL createContextualFragment should work even when the context is <menuitem> Fa iled to execute 'createContextualFragment' on 'Range': The range's container is 'menuitem', which is not supported.
26 FAIL createContextualFragment should work even when the context is <image> Faile d to execute 'createContextualFragment' on 'Range': The range's container is 'im age', which is not supported.
27 PASS <html> and <body> must work the same, 1
28 PASS <html> and <body> must work the same, 2
29 PASS Implicit <body> creation
30 PASS Namespace generally shouldn't matter
31 PASS <html> in a different namespace shouldn't be special
32 PASS SVG namespace shouldn't be special
33 PASS null should be stringified
34 PASS undefined should be stringified
35 PASS Text nodes shouldn't be special
36 PASS Non-Element parent should not be special
37 Harness: the test ran to completion.
38
OLDNEW
« no previous file with comments | « no previous file | third_party/WebKit/LayoutTests/external/wpt/html/syntax/serializing-html-fragments/serializing-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698