Bug 76563

Summary: [Qt] DumpRenderTree converts "file:///" to a path differently
Product: WebKit Reporter: Alexey Proskuryakov <ap>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: kadam, ossy
Priority: P2 Keywords: Qt, QtTriaged
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 76496    

Description Alexey Proskuryakov 2012-01-18 12:22:15 PST
iframe-invalid-source-crash.html and bubble-drag-events.html tests fail on Qt, apparently because file URLs are dumped differently than on Mac.

-CONSOLE MESSAGE: Not allowed to load local resource: /
+CONSOLE MESSAGE: Not allowed to load local resource:
Comment 1 Csaba Osztrogonác 2012-01-18 13:35:44 PST
Only http/tests/misc/iframe-invalid-source-crash.html has this bug, the other one works fine. I skipped it to make bot happier, and will check DRT later. ( http://trac.webkit.org/changeset/105313 )
Comment 2 Csaba Osztrogonác 2012-01-19 05:07:24 PST
There is one more failing test because of this bug: http/tests/misc/drag-over-iframe-invalid-source-crash.html (But it is still skipped on qt-wk1, because it fails with time out. But it worked on qt-wk2 previously, now it fails.)

I skipped it too: http://trac.webkit.org/changeset/105405/trunk/LayoutTests/platform/qt/Skipped
Comment 3 Alexey Proskuryakov 2012-01-19 11:58:24 PST
Fixing the same for WK2 in bug 76653.
Comment 4 Ádám Kallai 2012-10-04 06:32:30 PDT
 * http/tests/misc/drag-over-iframe-invalid-source-crash.html
 * http/tests/misc/iframe-invalid-source-crash.html

These tests are working on Qt-Wk2, still fails on Qt-Wk1. I added to Qt-Wk1 TestExpectations.

Committed r130385: <http://trac.webkit.org/changeset/130385>
Comment 5 Jocelyn Turcotte 2014-02-03 03:19:44 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.