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

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

From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 Nov 2017 16:38:24 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-346085203-1511282303-sysbot+gh@w3.org>
No. The test is creating those coalesced events with the same dictionary. With the exception of target the rest of the attributes are being set of the same dictionary and hence are the same. However, I remember @smaug---- mentioning about the target and I did tell him that in Chrome we do set the target of all the events including the target. To me target is a little different as js doesn't set it explicitly. They just fire the event to a target and user agent sets the target attribute as well as other related attributes affected by the target like offsetX/Y of the events. So we extend this model to include coalesced events as well. Would it make sense? Do you have any suggestion on the spec to make it clearer if you believe this behavior is reasonable?

-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/229#issuecomment-346085203 using your GitHub account
Received on Tuesday, 21 November 2017 16:38:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 November 2017 16:38:27 UTC