Bug 76563 - [Qt] DumpRenderTree converts "file:///" to a path differently
: [Qt] DumpRenderTree converts "file:///" to a path differently
: WebKit
Tools / Tests
: 528+ (Nightly build)
: Unspecified Unspecified
: P2 Normal
Assigned To:
: Qt, QtTriaged
: 76496
  Show dependency treegraph
Reported: 2012-01-18 12:22 PST by
Modified: 2014-02-03 03:19 PST (History)



You need to log in before you can comment on or make changes to this bug.

Description From 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 From 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 From 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 From 2012-01-19 11:58:24 PST -------
Fixing the same for WK2 in bug 76653.
------- Comment #4 From 2012-10-04 06:32:30 PST -------
 * 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 From 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.