Bug 77729 - [Qt] fast/events/touch/emulate-touch-events.html fails
Summary: [Qt] fast/events/touch/emulate-touch-events.html fails
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Keywords: Qt, QtTriaged
Depends on:
Blocks: 77105
  Show dependency treegraph
Reported: 2012-02-03 05:05 PST by Zoltan Arvai
Modified: 2014-02-03 03:19 PST (History)
3 users (show)

See Also:

skip (1.09 KB, patch)
2012-02-03 05:15 PST, Zoltan Arvai
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Zoltan Arvai 2012-02-03 05:05:40 PST
It seems that the newly added layout test in r106642
not running as expected on Qt Linux Release bot:

--- /ramdisk/qt-linux-release/build/layout-test-results/fast/events/touch/emulate-touch-events-expected.txt 
+++ /ramdisk/qt-linux-release/build/layout-test-results/fast/events/touch/emulate-touch-events-actual.txt 
@@ -52,8 +52,8 @@
 PASS lastEvent.changedTouches[0].clientY is 30
 PASS lastEvent.changedTouches[0].identifier is 0
 PASS lastEvent.shiftKey is false
-PASS lastEvent.altKey is true
-PASS lastEvent.ctrlKey is true
+FAIL lastEvent.altKey should be true. Was false.
+FAIL lastEvent.ctrlKey should be true. Was false.
 PASS lastEvent.metaKey is false
 PASS successfullyParsed is true

Comment 1 Zoltan Arvai 2012-02-03 05:15:58 PST
Created attachment 125311 [details]
Comment 2 Csaba Osztrogonác 2012-02-03 05:18:55 PST
Comment on attachment 125311 [details]

Comment 3 Csaba Osztrogonác 2012-02-03 05:23:40 PST
Comment on attachment 125311 [details]

Clearing flags on attachment: 125311

Committed r106652: <http://trac.webkit.org/changeset/106652>
Comment 4 Jocelyn Turcotte 2014-02-03 03:19:54 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.