Chromium Code Reviews| Index: third_party/WebKit/LayoutTests/fast/dom/Window/orphaned-frame-access-expected.txt |
| diff --git a/third_party/WebKit/LayoutTests/fast/dom/Window/orphaned-frame-access-expected.txt b/third_party/WebKit/LayoutTests/fast/dom/Window/orphaned-frame-access-expected.txt |
| index 8157e5507f099fd04a5d8c27f49c8b626f7aaabb..b0c32f76bef7e7324a8fb89af39bcdc825e56418 100644 |
| --- a/third_party/WebKit/LayoutTests/fast/dom/Window/orphaned-frame-access-expected.txt |
| +++ b/third_party/WebKit/LayoutTests/fast/dom/Window/orphaned-frame-access-expected.txt |
| @@ -1,12 +1,6 @@ |
| -This tests access to a window with a null frame. You should see "PASS" for each of the three tests below. |
| - |
| -On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". |
| - |
| - |
| -missing property: PASS |
| -missing array index: PASS |
| -missing interface object: PASS |
| -PASS successfullyParsed is true |
| - |
| -TEST COMPLETE |
| +This is a testharness.js-based test. |
| +PASS Named property access on detached Window |
| +FAIL Indexed property access on detached Window assert_equals: Indexed property should still be accessible. expected (string) "123" but got (undefined) undefined |
|
dcheng
2017/05/15 06:15:32
I'm not really sure why, but this behavior seems t
Yuki
2017/05/15 06:55:27
Probably, this is caused by the revert at
https://
|
| +PASS Interface Object access on detached Window |
| +Harness: the test ran to completion. |