- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Tue, 17 Jun 2014 06:56:23 -0400
- To: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Hi All - sorry for the late notice but there will be no PEWG call on June 17. Let's do plan to have a call on June 24. Regarding completing the test suite, Scott's email below provides some of the related actions for some open PRs. We should all follow up on that thread. Another test related action is to update the Test Status column of [TestAssertions]. If we now have a merged test, the status could be labeled something like "Yes" and then link directly to the "live" test in [w-p-t] or its location on the [master] branch. WDYT? Is anyone willing to do this? -Thanks, AB [TestAssertions] <https://www.w3.org/wiki/PointerEvents/TestAssertions> [w-p-t] <http://w3c-test.org/pointerevents> [master] <https://github.com/w3c/web-platform-tests/tree/master/pointerevents> -------- Original Message -------- Subject: Re: ACTION-108: Send a todo list re testing that needs to be done (Pointer Events Working Group) Resent-Date: Sat, 14 Jun 2014 01:18:18 +0000 Resent-From: public-pointer-events@w3.org Date: Fri, 13 Jun 2014 21:17:49 -0400 From: Scott González <scott.gonzalez@gmail.com> To: Pointer Events Working Group <public-pointer-events@w3.org> I believe the following is the full list of assertions from the TTWF event that haven't been already implemented in web-platform-tests. TA 3.1, 3.2 - pointerup properties matching pointerdown properties https://github.com/dmethvin/pointerevents-test/blob/6d1a680451dcacb23ccfeb907c024a124ab3a8ec/pointerup.html#L133 We do have the equivalent tests for pointermove (5.1, 5.2) in pointerevent_pointermove_isprimary_same_as_pointerdown.html TA 12.1 - constructor assertions https://github.com/dmethvin/pointerevents-test/blob/master/constructor.html There are more extensive pointerleave tests with deeply nested elements, but I'm not sure if this is necessary: https://github.com/dmethvin/pointerevents-test/blob/master/pointerenterleave-continuous.html gotpointercapture and lostpointercapture events should be fired asynchronously. There is no Test Assertion for this, but this is covered by https://www.w3.org/Bugs/Public/show_bug.cgi?id=24971 gotpointercapture: https://github.com/dmethvin/pointerevents-test/blob/6d1a680451dcacb23ccfeb907c024a124ab3a8ec/pointercaptureevents.html#L106 lostpointercapture: https://github.com/dmethvin/pointerevents-test/blob/6d1a680451dcacb23ccfeb907c024a124ab3a8ec/pointercaptureevents.html#L129 On Tue, Jun 3, 2014 at 11:17 AM, Pointer Events Working Group Issue Tracker <sysbot+tracker@w3.org <mailto:sysbot+tracker@w3.org>> wrote: ACTION-108: Send a todo list re testing that needs to be done (Pointer Events Working Group) http://www.w3.org/2012/pointerevents/track/actions/108 On: Scott González Due: 2014-06-10 If you do not want to be notified on new action items for this group, please update your settings at: http://www.w3.org/2012/pointerevents/track/users/50558#settings
Received on Tuesday, 17 June 2014 10:56:50 UTC