Difference: * svg/hittest/zero-length-round-cap-path.xhtml --- /ramdisk/qt-linux-release/build/layout-test-results/svg/hittest/zero-length-round-cap-path-expected.txt +++ /ramdisk/qt-linux-release/build/layout-test-results/svg/hittest/zero-length-round-cap-path-actual.txt @@ -1,1 +1,1 @@ -PASSED; PASSED; PASSED; PASSED; PASSED; PASSED; PASSED; PASSED; +FAIL, hit [object SVGSVGElement] @ 5, 50; FAIL, hit [object SVGSVGElement] @ 95, 50; FAIL, hit [object SVGSVGElement] @ 50, 5; FAIL, hit [object SVGSVGElement] @ 50, 95; PASSED; PASSED; PASSED; PASSED; * svg/hittest/zero-length-square-cap-path.xhtml --- /ramdisk/qt-linux-release/build/layout-test-results/svg/hittest/zero-length-square-cap-path-expected.txt +++ /ramdisk/qt-linux-release/build/layout-test-results/svg/hittest/zero-length-square-cap-path-actual.txt @@ -1,1 +1,1 @@ -PASSED; PASSED; PASSED; PASSED; PASSED; PASSED; PASSED; PASSED; +FAIL, hit [object SVGSVGElement] @ 5, 50; FAIL, hit [object SVGSVGElement] @ 95, 50; FAIL, hit [object SVGSVGElement] @ 50, 5; FAIL, hit [object SVGSVGElement] @ 50, 95; FAIL, hit [object SVGSVGElement] @ 5, 5; FAIL, hit [object SVGSVGElement] @ 95, 5; FAIL, hit [object SVGSVGElement] @ 5, 95; FAIL, hit [object SVGSVGElement] @ 95, 95;
Thanks for reporting it. Could you add them to the Qt Skipped list until the expert check why they fail?
Created attachment 125817 [details] skip failing test (patch)
Comment on attachment 125817 [details] skip failing test (patch) rs=me. I'll land it manually.
Comment on attachment 125817 [details] skip failing test (patch) Clearing flags on attachment: 125817 Committed r106927: <http://trac.webkit.org/changeset/106927>
This is almost certainly related to https://bugs.webkit.org/show_bug.cgi?id=77020, because if the bounds are wrong on the zero length path, then the hit test will fail at the broad phase (test against bounding rect).
=== 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.