W3C home > Mailing lists > Public > public-pointer-events@w3.org > October to December 2017

[pointerevents] The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec

From: Stone via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 Nov 2017 09:19:07 +0000
To: public-pointer-events@w3.org
Message-ID: <issues.opened-275637638-1511255946-sysbot+gh@w3.org>
mingchou has just created a new issue for https://github.com/w3c/pointerevents:

== The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec ==
Spec says 'When the event is created by the user agent the following attributes of the coalesced events will always have the same value as the dispatched event'

The test case pointerevent_constructor.html dispatches a JS created event and expects that some attributes  (e.g. target, pointerId, pointerType, isPrimary) are set up as the same as the dispatched event. Looks like the test expects that these attributes are set up for all events no matter whether they are created by the UA or JS.

Wondering whether the behavior of the spec or the test case is expected?

Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/229 using your GitHub account
Received on Tuesday, 21 November 2017 09:19:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 November 2017 09:19:12 UTC