W3C home > Mailing lists > Public > public-webevents@w3.org > July to September 2012

TouchEvent test results for Chrome

From: Rick Byers <rbyers@chromium.org>
Date: Wed, 15 Aug 2012 15:15:27 -0400
Message-ID: <CAFUtAY9c5zPRNvA2WZb-ppKu_GRkHaq0NYB6KkmKgHO5Vwvg5A@mail.gmail.com>
To: public-webevents@w3.org, Matt Brubeck <mbrubeck@mozilla.com>
Cc: Robert Kroeger <rjkroege@chromium.org>, olilan@chromium.org
I've been playing with the touch event tests:

First of all, contrary to the discussion on the recent telcon about "manual
tests being oldschool", I quite like this test infrastructure.  It makes it
very easy to test any browser on any device, and it is really quite simple
(one simple user action triggering lots of test cases).  Thanks Matt!  Now
I'd like to try to extend the infrastructure to also support automated
testing when run in a suitable environment that can simulate touches (eg.
as a WebKit layout test).  I'll try to experiment with adding that at some
point (although in practice sharing code with WebKit layout tests may be
more trouble than it's worth).

I ran the tests on current chrome (22.0.1229.6, canary channel) on
ChromeOS, as well as on current released Chrome for Android builds.  I got
the same result in both cases (in itself a nice surprise for me <grin>).
 All 6 of the multi-touch tests passed.  I got 5 failures in the
single-touch tests:

ResultTest Name Message1. Fail touchstart TouchEvent target attributes are
correct.assert_equals:relatedTarget must be null for touchstart event.
expected null but got undefined
2. Fail Interface names are correct.TouchList is not defined 3. Fail
identifiedTouch Object #<TouchList> has no method 'identifiedTouch'4.
Fail Touch
attribute values are valid assert_true:rotationAngle must be >= 0.
expected true got false
5. Fail Touch attribute values are validassert_true:rotationAngle must be
>= 0.
expected true got false

My analysis:
#1: relatedTarget is defined in TouchEvents v2, so should be removed from
this test suite (Matt, I think you mentioned that already).
#2: Looks like a bug in Chrome.  The object does appear to be a TouchList,
not sure offhand why it's not defined.  I filed http://crbug.com/142936 to
myself to dig into this and presumably fix it in WebKit.
#3: Looks like a missing feature in WebKit.  I've filed
http://crbug.com/142938 to myself to add this.
#4/#5: rotationAngle is undefined, but it's part of TouchEvents v2 so again
I think we should remove this part of the test.  Also we should update the
test names to make it clear the first is for the touchstart and the 2nd is
for the touchend (maybe avoid the code duplication too).

Received on Wednesday, 15 August 2012 19:16:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:09:34 UTC