RESOLVED INVALID 103122
[Qt][WK2] New fast/events/mouse-cursor.html fails 
https://bugs.webkit.org/show_bug.cgi?id=103122
Summary [Qt][WK2] New fast/events/mouse-cursor.html fails
Csaba Osztrogonác
Reported 2012-11-23 04:01:52 PST
fast/events/mouse-cursor.html introduced in http://trac.webkit.org/changeset/134874 but fails on Qt WK2 with the following diff: --- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/fast/events/mouse-cursor-expected.txt +++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/fast/events/mouse-cursor-actual.txt @@ -19,61 +19,61 @@ Cursor Info: type=None hotSpot=0,0 TEST CASE: Pointer -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: -webkit-grabbing -Cursor Info: type=Grabbing hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Existing 25x25 image -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Invalid URL with fallback to pointer -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Invalid with fallback to 25x25 image -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with explicit hot spot at (0,0) -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with explicit hot spot at (20,10) -Cursor Info: type=Custom hotSpot=20,10 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with explicit hot spot at (-1,-1) -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with explicit hot spot outside image at (30,30) -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with implicit hot spot at (5,4) -Cursor Info: type=Custom hotSpot=5,4 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with explicit hot spot at (20,10) overriding implicit hot spot -Cursor Info: type=Custom hotSpot=20,10 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Image with implicit hot spot outside image at (35,4) -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Over large image with fallback to pointer -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: SVG cursor -Cursor Info: type=Custom hotSpot=0,0 image=25x25 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Multiple invalid cursors with fallback to pointer -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Nonexistent SVG cursor with fallback to pointer -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: A link with default cursor -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Link with default cursor overriding wait -Cursor Info: type=Hand hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 TEST CASE: Wait cursor which should not be affected by unknown cursor rule -Cursor Info: type=Wait hotSpot=0,0 +Cursor Info: type=None hotSpot=0,0 PASS successfullyParsed is true
Attachments
Add attachment proposed patch, testcase, etc.
Csaba Osztrogonác
Comment 1 2012-11-23 04:10:23 PST
I skipped it to paint the bot green - r135589. Please unskip it with the proper fix.
Rick Byers
Comment 2 2012-11-23 18:34:56 PST
I added that test and would be happy to help someone who works on the Qt port to figure out what's going on (I've never built Qt myself). Is changing mouse cursors actually working in Qt Wk2? If so, then I'd guess that either: - EventSender isn't properly wired up to send fake mouse move events for the layout test, or - EventHandler::selectMouseCursor doesn't get called on mouse move in this port (so EventHandler::m_currentMouseCursor isn't updated).
Jocelyn Turcotte
Comment 3 2014-02-03 03:23:43 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.