Re: [domparsing-tests] Test that createContextualFragment works on a variety of contexts (#4403)

# Chrome #
Testing revision 9f7bff548002b1c40293c14254ada62a7431687a
Starting 10 test iterations
All results were stable

## All results ##

<details>

<summary><a href="http://w3c-test.org/submissions/4403/domparsing/createContextualFragment.html">/domparsing/createContextualFragment.html</a></summary>


|                                  Subtest                                   | Results |
|----------------------------------------------------------------------------|---------|
|                                                                            | OK      |
| `Text nodes shouldn't be special`                                          | PASS    |
| `Simple test with paragraphs`                                              | PASS    |
| `createContextualFragment should work even when the context is <menuitem>` | PASS    |
| `SVG namespace shouldn't be special`                                       | PASS    |
| `<html> in a different namespace shouldn't be special`                     | PASS    |
| `createContextualFragment should work even when the context is <input>`    | FAIL    |
| `createContextualFragment should work even when the context is <image>`    | FAIL    |
| `createContextualFragment should work even when the context is <meta>`     | FAIL    |
| `createContextualFragment should work even when the context is <bgsound>`  | PASS    |
| `Implicit <body> creation`                                                 | PASS    |
| `createContextualFragment should work even when the context is <basefont>` | FAIL    |
| `<script>s should be run when appended to the document (but not before)`   | PASS    |
| `createContextualFragment should work even when the context is <wbr>`      | FAIL    |
| `createContextualFragment should work even when the context is <br>`       | FAIL    |
| `createContextualFragment should work even when the context is <area>`     | FAIL    |
| `createContextualFragment should work even when the context is <track>`    | FAIL    |
| `createContextualFragment should work even when the context is <img>`      | FAIL    |
| `undefined should be stringified`                                          | PASS    |
| `createContextualFragment should work even when the context is <frame>`    | FAIL    |
| `Don't auto-create <body> when applied to <html>`                          | PASS    |
| `Namespace generally shouldn't matter`                                     | PASS    |
| `Non-Element parent should not be special`                                 | PASS    |
| `createContextualFragment should work even when the context is <link>`     | FAIL    |
| `Must throw TypeError when calling without arguments`                      | PASS    |
| `Must not throw INVALID_STATE_ERR for a detached node.`                    | PASS    |
| `createContextualFragment should work even when the context is <base>`     | FAIL    |
| `createContextualFragment should work even when the context is <col>`      | FAIL    |
| `createContextualFragment should work even when the context is <embed>`    | FAIL    |
| `<html> and <body> must work the same, 1`                                  | PASS    |
| `<html> and <body> must work the same, 2`                                  | PASS    |
| `createContextualFragment should work even when the context is <source>`   | FAIL    |
| `createContextualFragment should work even when the context is <param>`    | FAIL    |
| `createContextualFragment should work even when the context is <hr>`       | FAIL    |
| `createContextualFragment should work even when the context is <keygen>`   | FAIL    |
| `null should be stringified`                                               | PASS    |

</details>


View on GitHub: https://github.com/w3c/web-platform-tests/pull/4403#issuecomment-269555084

Received on Tuesday, 10 January 2017 21:46:27 UTC