REOPENED Bug 161143
[ios-simulator] LayoutTest imported/w3c/web-platform-tests/html/browsers/browsing-the-web/history-traversal/persisted-user-state-restoration/scroll-restoration-fragment-scrolling-samedoc.html failing 
https://bugs.webkit.org/show_bug.cgi?id=161143
Summary [ios-simulator] LayoutTest imported/w3c/web-platform-tests/html/browsers/brow...
Ryan Haddad
Reported 2016-08-24 09:47:14 PDT
[ios-simulator] LayoutTest imported/w3c/web-platform-tests/html/browsers/browsing-the-web/history-traversal/persisted-user-state-restoration/scroll-restoration-fragment-scrolling-samedoc.html failing --- /Volumes/Data/slave/ios-simulator-9-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/browsers/browsing-the-web/history-traversal/persisted-user-state-restoration/scroll-restoration-fragment-scrolling-samedoc-expected.txt +++ /Volumes/Data/slave/ios-simulator-9-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/browsers/browsing-the-web/history-traversal/persisted-user-state-restoration/scroll-restoration-fragment-scrolling-samedoc-actual.txt @@ -1,3 +1,3 @@ -FAIL Manual scroll restoration should take precedent over scrolling to fragment in cross doc navigation assert_equals: should not scroll to fragment expected 0 but got 800 +PASS Manual scroll restoration should take precedent over scrolling to fragment in cross doc navigation https://build.webkit.org/builders/Apple%20iOS%209%20Simulator%20Debug%20WK2%20(Tests)/builds/4517
Attachments
Add attachment proposed patch, testcase, etc.
Ryan Haddad
Comment 1 2016-08-24 09:49:59 PDT
Looks like there is no iOS specific expected file, maybe we need one?
Chris Dumez
Comment 2 2016-08-24 09:50:44 PDT
(In reply to comment #1) > Looks like there is no iOS specific expected file, maybe we need one? Yes, there should be.
Ryan Haddad
Comment 3 2016-08-24 10:18:00 PDT
Done in https://trac.webkit.org/r204903.
Ryan Haddad
Comment 4 2016-08-24 13:11:03 PDT
Reopening because it now appears that this test is flaky.
Note You need to log in before you can comment on or make changes to this bug.