RESOLVED INVALID 99148
[Qt][WK2] http/tests/misc/willCacheResponse-delegate-callback.html fails 
https://bugs.webkit.org/show_bug.cgi?id=99148
Summary [Qt][WK2] http/tests/misc/willCacheResponse-delegate-callback.html fails
Csaba Osztrogonác
Reported 2012-10-12 00:58:00 PDT
--- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/misc/willCacheResponse-delegate-callback-expected.txt +++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/misc/willCacheResponse-delegate-callback-actual.txt @@ -1,5 +1,4 @@ http://127.0.0.1:8000/misc/resources/willCacheResponse-success.html - willSendRequest <NSURLRequest URL http://127.0.0.1:8000/misc/resources/willCacheResponse-success.html, main document URL http://127.0.0.1:8000/misc/willCacheResponse-delegate-callback.html, http method GET> redirectResponse (null) -http://127.0.0.1:8000/misc/resources/willCacheResponse-success.html - willCacheResponse: called http://127.0.0.1:8000/misc/resources/willCacheResponse-success.html - didReceiveResponse <NSURLResponse http://127.0.0.1:8000/misc/resources/willCacheResponse-success.html, http status code 200> This tests for the willCacheResponse resource delegate callback as added for radar 5008925. The test is only meaningful if you are running it under DumpRenderTree
Attachments
Add attachment proposed patch, testcase, etc.
Csaba Osztrogonác
Comment 1 2012-10-12 05:42:14 PDT
I skipped it by https://trac.webkit.org/changeset/131177. Please unskip it with the proper fix.
Jocelyn Turcotte
Comment 2 2014-02-03 03:22:56 PST
=== 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.
Note You need to log in before you can comment on or make changes to this bug.