RE: Need test results against Jan 2013 Touch Events LC

A few comments...

We should call out that the test data are for the Jan 2013 LCWD. Although
there's a link to that, the text that specifically mentions the Dec 2011 CR
(about the exit criteria) can be confusing and misleading.

The Firefox result was 51 pass + 2 fail in initial my report. Since Matt
reported that one of those failures have been fixed in Nightly 22, the final
result should be 52 pass + 1 fail.

Also, the Opera result should be 52 pass + 1 fail. This seems to be just a
typo.

Regards, Cathy.


> -----Original Message-----
> From: Barstow Art (Nokia-CIC/Boston)
> Sent: Sunday, February 24, 2013 2:33 PM
> To: Matt Brubeck; Chan Cathy (Nokia-CIC/Boston); public-
> webevents@w3.org
> Subject: Re: Need test results against Jan 2013 Touch Events LC
> 
> Thanks for the data Cathy and Matt.
> 
> It appears we now have at least two implementations that pass each test,
> and if so, Touch Events v1 can now proceed directly to Proposed
> Recommendation (and skip another Candidate Recommendation).
> 
> Based on the data in this thread, I created an Implementation Report
> <http://www.w3.org/2010/webevents/wiki/TEv1ImplReport>.
> 
> Everyone - please review this document and send comments.
> 
> -Thanks, Art
> 
> 
> On 2/22/13 4:36 PM, ext Matt Brubeck wrote:
> > On 2/22/2013 1:03 PM, Cathy.Chan@nokia.com wrote:
> >> With Firefox on Android (v19.0):
> >> * create-touch-touchlist - 51 passes + 2 fails
> >> - document.createTouch exists and creates a Touch object with
> >> requested properties | assert_equals: touch.clientY is
> >> touch.pageY-window.pageYOffset.
> >> | expected 15 but got 0
> > In the latest Firefox Nightly (22.0a1) on both Android and Windows, I
> > do not see this failure but I see an almost identical one
> > ("assert_equals: touch.clientX is touch.pageX - window.pageXOffset.
> > expected 15 but got 0").
> >
> > This is a Firefox bug.  Gecko defines createTouch differently from the
> > v1 spec:
> > http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/events/ns
> > IDOMTouchEvent.idl#83
> >
> >
> >> - document.createTouchList exists and correctly creates a TouchList
> >> from two Touch objects | assert_equals: touchList.length is 2 |
> >> expected 2 but got 1
> >> ---> This arises from the API change and is something we expect to be
> >> updated in the next release.
> > I verified this is fixed in Firefox Nightly 22 (and in the
> > soon-to-be-released Firefox Aurora 21).