Chromium Code Reviews| Index: LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt |
| diff --git a/LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt b/LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt |
| index 1eca51ac7914b020644f12adea12d27a34ec29ec..2bed17e13f38af533b6d8c604fbc7fb5a8fad673 100644 |
| --- a/LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt |
| +++ b/LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt |
| @@ -1,4 +1,3 @@ |
| -It looks like the browser stopped loading the page when encountering a .go(-1) command pointing to a pushed state. This will break the tests. |
|
jsbell
2015/06/02 17:34:21
Is this bogus, anything we need to investigate, or
tkent
2015/06/02 20:41:15
I think the FAIL lines are due to this behavior.
|
| This is a testharness.js-based test. |
| PASS history.state should initially be null |
| PASS history.pushState support is needed for this testcase |