W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2013

Re: Invalid Test Assertions

From: Scott González <scott.gonzalez@gmail.com>
Date: Thu, 27 Jun 2013 13:53:15 -0400
Message-ID: <CAO8i3id4rYJZyW6ij4FcaHair3VxkzMRh0vxU0zDNSbGz8iGUQ@mail.gmail.com>
To: Charles McCathie Nevile <chaals@yandex-team.ru>
Cc: Arthur Barstow <art.barstow@nokia.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
I've updated the Test Assertions page as well as the associated pull
request [1].

[1] https://github.com/w3c/web-platform-tests/pull/107


On Wed, Jun 26, 2013 at 6:00 PM, Charles McCathie Nevile <
chaals@yandex-team.ru> wrote:

> On Thu, 27 Jun 2013 01:27:12 +0400, Arthur Barstow <art.barstow@nokia.com>
> wrote:
>
>  On 6/26/13 2:24 PM, ext Scott González wrote:
>>
>>> We have two test assertions (1.11, 1.12) which deal with pointerId being
>>> restricted to 1 for mouse. Since we have tests that reference the test
>>> assertions by number, how do we handle removing these from the list? Do we
>>> keep them numbered 1.11 and 1.12 and strike them out? Or do we delete them
>>> and renumber 1.13?
>>>
>>
>> My recommendation is to just strike those two IDs (so any references to
>> ID 1.13 do not have to be updated).
>>
>
> Yep, I agree.
>
> (Them URI things gotta be useful for something...)
>
> cheers
>
>
>  Once we have a resolution on this, I will update the Test Assertion page
>>> [1] and update the tests.
>>>
>>
>> By June 27, if you don't hear any objections to `striking`, please go
>> ahead and update [1] accordingly and update the tests.
>>
>> -Thanks! Art
>>
>>  [1] http://www.w3.org/wiki/**PointerEvents/TestAssertions<http://www.w3.org/wiki/PointerEvents/TestAssertions>
>>>
>>
>>
>>
>
> --
> Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
>       chaals@yandex-team.ru         Find more at http://yandex.com
>
Received on Thursday, 27 June 2013 17:59:17 UTC

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