W3C Test: Import web-platform-tests/html/browsers

LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt

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
new file mode 100644
index 0000000000000000000000000000000000000000..1eca51ac7914b020644f12adea12d27a34ec29ec
--- /dev/null
+++ b/LayoutTests/imported/web-platform-tests/html/browsers/history/the-history-interface/007-expected.txt
@@ -0,0 +1,12 @@
+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.
+This is a testharness.js-based test.
+PASS history.state should initially be null 
+PASS history.pushState support is needed for this testcase 
+PASS history.state should reflect pushed state 
+FAIL popstate event should fire before onload fires assert_true: expected true got false
+FAIL the correct state should be restored when navigating during initial load assert_equals: expected (string) "state1" but got (boolean) false
+FAIL history.state should reflect the navigated state onload assert_equals: expected "state1" but got "state2"
+FAIL popstate event should not fire after onload fires assert_false: expected false got true
+PASS history.state should reflect the navigated state after onload 
+Harness: the test ran to completion.
+