62731 2011-06-15 08:38:43 -0700 [Qt][WK2] http/tests/loading/state-object-security-exception.html fails 2014-02-03 03:17:58 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) All All RESOLVED INVALID Qt, QtTriaged P2 Normal --- 1 ossy webkit-unassigned feherzs jesus kbalazs ossy oldest_to_newest 421320 0 ossy 2011-06-15 08:38:43 -0700 --- /tmp/layout-test-results/http/tests/loading/state-object-security-exception-expected.txt 2011-06-15 15:41:22.779090505 +0000 +++ /tmp/layout-test-results/http/tests/loading/state-object-security-exception-actual.txt 2011-06-15 15:41:22.779090505 +0000 @@ -1,8 +1,3 @@ -main frame - didStartProvisionalLoadForFrame -main frame - didCommitLoadForFrame -main frame - didFinishDocumentLoadForFrame -main frame - didHandleOnloadEventsForFrame -main frame - didFinishLoadForFrame This test makes sure that calls to pushState() and replaceState() with URLs that violate the security origin check fail as expected. Trying to pushState() with url http://localhost/test.html failed with exception Error: SECURITY_ERR: DOM Exception 18 548931 1 jesus 2012-02-03 12:13:08 -0800 This test passes locally to me but I'm a bit confused. From wk2/Skipped: # WebKitTestRunner needs layoutTestController.clearBackForwardList # <https://bugs.webkit.org/show_bug.cgi?id=42333> fast/dom/location-hash.html fast/history/form-submit-in-frame-via-onclick.html fast/history/form-submit-in-frame.html fast/history/gesture-before-onload-form-submit.html fast/history/gesture-before-onload-location-href.html fast/history/history-length.html fast/history/redirect-via-iframe.html fast/loader/location-port.html fast/loader/stateobjects/document-destroyed-navigate-back-with-fragment-scroll.html fast/loader/stateobjects/document-destroyed-navigate-back.html fast/loader/stateobjects/popstate-after-load-complete-addeventlistener.html fast/loader/stateobjects/popstate-after-load-complete-body-attribute.html fast/loader/stateobjects/popstate-after-load-complete-body-inline-attribute.html fast/loader/stateobjects/popstate-after-load-complete-window-attribute.html fast/loader/stateobjects/pushstate-clears-forward-history.html fast/loader/stateobjects/pushstate-then-replacestate.html fast/loader/stateobjects/pushstate-updates-location.html fast/loader/stateobjects/pushstate-with-fragment-urls-and-hashchange.html fast/loader/stateobjects/pushstate-within-popstate-handler-assert.html fast/loader/stateobjects/pushstate-without-history.html fast/loader/stateobjects/replacestate-then-pushstate.html http/tests/loading/state-object-security-exception.html However, https://bugs.webkit.org/show_bug.cgi?id=42333 was marked as RESOLVED FIXED on 27/10/2010. I have checked it quickly and the other tests seem to be passing here locally as well, Ossy. Is there a special reason for this to be skipped for everyone? (since it's skipped in wk2/Skipped) 549386 2 ossy 2012-02-04 00:11:43 -0800 I think there isn't a good reason why these tests are still in the skipped list. rs=me to unskip them. But please check our WK2 bot and Mac WK2 bot to ensure these tests are passing. 550044 3 jesus 2012-02-06 09:05:52 -0800 Committed r106812: <http://trac.webkit.org/changeset/106812> 550139 4 jesus 2012-02-06 11:38:29 -0800 Committed r106825: <http://trac.webkit.org/changeset/106825> 550146 5 jesus 2012-02-06 11:43:23 -0800 (In reply to comment #3) > Committed r106812: <http://trac.webkit.org/changeset/106812> I skipped all those tests on this commit. (In reply to comment #4) > Committed r106825: <http://trac.webkit.org/changeset/106825> But then on this commit I had to skip the following tests: Regressions: Unexpected text diff mismatch : (3) fast/history/form-submit-in-frame-via-onclick.html = TEXT fast/history/form-submit-in-frame.html = TEXT http/tests/loading/state-object-security-exception.html = TEXT I'm keeping the bug open until someone can investigate this. 975233 6 jturcotte 2014-02-03 03:17:58 -0800 === Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.