Bug 60497

Summary: [Qt] tst_QWebPage creates temporary files in the current working dir
Product: WebKit Reporter: Ademar Reis <ademar>
Component: WebKit QtAssignee: Ademar Reis <ademar>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, commit-queue, eric, webkit.review.bot
Priority: P5 Keywords: Qt
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Ademar Reis
Reported 2011-05-09 12:44:36 PDT
[Qt] tst_QWebPage creates temporary files in the current working dir
Attachments
Patch (4.76 KB, patch)
2011-05-09 12:45 PDT, Ademar Reis 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Ademar Reis
Comment 1 2011-05-09 12:45:29 PDT
Created attachment 92831 [details] Patch
Alexis Menard (darktears)
Comment 2 2011-05-10 07:22:33 PDT
Comment on attachment 92831 [details] Patch Looks good to me.
Csaba Osztrogonác
Comment 3 2011-05-10 07:58:02 PDT
Comment on attachment 92831 [details] Patch LGTM, r=me
WebKit Commit Bot
Comment 4 2011-05-10 08:31:51 PDT
The commit-queue encountered the following flaky tests while processing attachment 92831 [details]: http/tests/xmlhttprequest/cross-origin-authorization.html bug 52398 (author: ap@webkit.org) The commit-queue is continuing to process your patch.
WebKit Commit Bot
Comment 5 2011-05-10 08:32:56 PDT
Comment on attachment 92831 [details] Patch Clearing flags on attachment: 92831 Committed r86154: <http://trac.webkit.org/changeset/86154>
WebKit Commit Bot
Comment 6 2011-05-10 08:33:00 PDT
All reviewed patches have been landed. Closing bug.
WebKit Review Bot
Comment 7 2011-05-10 10:53:19 PDT
http://trac.webkit.org/changeset/86154 might have broken SnowLeopard Intel Release (WebKit2 Tests) The following tests are not passing: fast/frames/flattening/frameset-flattening-subframesets.html
Ademar Reis
Comment 8 2011-06-01 12:32:12 PDT
Revision r86154 cherry-picked into qtwebkit-2.2 with commit 787bda5 <http://gitorious.org/webkit/qtwebkit/commit/787bda5>
Note You need to log in before you can comment on or make changes to this bug.