Bug 140250 - Layout Test fast/loader/stateobjects/document-destroyed-navigate-back-with-fragment-scroll.html is failing
Summary: Layout Test fast/loader/stateobjects/document-destroyed-navigate-back-with-fr...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-08 09:51 PST by Brent Fulgham
Modified: 2015-10-12 12:07 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Fulgham 2015-01-08 09:51:39 PST 
The following layout tests are failing on Windows.

fast/loader/stateobjects/document-destroyed-navigate-back-with-fragment-scroll.html
fast/loader/stateobjects/document-destroyed-navigate-back.html

Problem seems to be related to missing annulled handler.

Failure is:

--- /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/loader/stateobjects/document-destroyed-navigate-back-with-fragment-scroll-expected.txt
+++ /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/loader/stateobjects/document-destroyed-navigate-back-with-fragment-scroll-actual.txt
@@ -5,9 +5,6 @@
 ALERT: State popped - SecondEntry (type string)
 ALERT: hashChanged - Last path component of location is document-destroyed-navigate-back-with-fragment-scroll.html#SecondEntry
 ALERT: Navigating back...
-main frame - has 1 onunload handler(s)
-ALERT: LOADED
-ALERT: Last path component of location is document-destroyed-navigate-back-with-fragment-scroll.html#SecondEntryWillLaterBeReactivated
 ALERT: State popped - SecondEntryWillLaterBeReactivated (type string)
 ALERT: State popped - FirstEntryWillLaterBeReactivated (type string)
 ALERT: hashChanged - Last path component of location is document-destroyed-navigate-back-with-fragment-scroll.html#FirstEntryWillLaterBeReactivated

--- /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/loader/stateobjects/document-destroyed-navigate-back-expected.txt
+++ /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/loader/stateobjects/document-destroyed-navigate-back-actual.txt
@@ -2,8 +2,6 @@
 ALERT: State popped - FirstEntry (type string)
 ALERT: State popped - SecondEntry (type string)
 ALERT: Navigating back...
-main frame - has 1 onunload handler(s)
-ALERT: Last path component of location is document-destroyed-navigate-back.html?SecondEntryWillLaterBeReactivated
 ALERT: State popped - SecondEntryWillLaterBeReactivated (type string)
 ALERT: State popped - FirstEntryWillLaterBeReactivated (type string)
 ALERT: Test complete
Comment 1 Brent Fulgham 2015-01-08 09:56:32 PST 
The following test seems to suffer from the same problem:

fast/loader/stateobjects/replacestate-in-iframe.html

--- /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/loader/stateobjects/replacestate-in-iframe-expected.txt
+++ /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/loader/stateobjects/replacestate-in-iframe-actual.txt
@@ -1,7 +1,5 @@
 main frame - has 1 onunload handler(s)
 frame "<!--framePath //<!--frame0-->-->" - has 1 onunload handler(s)
 ALERT: Navigating back...
-main frame - has 1 onunload handler(s)
-frame "<!--framePath //<!--frame0-->-->" - has 1 onunload handler(s)
 ALERT: onpopstate
 PASS
Comment 2 Brent Fulgham 2015-07-24 21:07:55 PDT 
This doesn't seem to be failing anymore.
Comment 3 Brent Fulgham 2015-10-12 12:07:52 PDT 
The loader and cache changes made this cycle seem to have fixed these bugs:

fast/loader/stateobjects/replacestate-in-iframe.html 
fast/loader/stateobjects/document-destroyed-navigate-back.html
fast/loader/stateobjects/document-destroyed-navigate-back-with-fragment-scroll.html