Chromium Code Reviews| Index: third_party/WebKit/LayoutTests/custom-elements/spec/upgrade-element-expected.txt |
| diff --git a/third_party/WebKit/LayoutTests/custom-elements/spec/upgrade-element-expected.txt b/third_party/WebKit/LayoutTests/custom-elements/spec/upgrade-element-expected.txt |
| deleted file mode 100644 |
| index a479d42fbdcec097e0736ac3a969d91d6a748b72..0000000000000000000000000000000000000000 |
| --- a/third_party/WebKit/LayoutTests/custom-elements/spec/upgrade-element-expected.txt |
| +++ /dev/null |
| @@ -1,7 +0,0 @@ |
| -This is a testharness.js-based test. |
|
dominicc (has gone to gerrit)
2016/07/22 07:34:08
Yay.
|
| -PASS "connectedCallback", "attributeChangedCallback" reactions should execute after the constructor |
| -PASS The constructor non-conformatly uses API decorated with the [CEReactions] |
| -FAIL Upgrading an element with a throwing constructor should rethrow that exception assert_array_equals: rethrow any exception thrown from constructor property 0, expected "constructor throws" but got object "Error: assert_false: calling super() with non-empty construction stack should not define the element expected false got true" |
| -FAIL Upgrading an element with invalid constructor assert_array_equals: returning object that is different from element should throw "InvalidStateError" lengths differ, expected 1 got 0 |
| -Harness: the test ran to completion. |
| - |