- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 May 2017 16:48:59 +0000
- To: public-pointer-events@w3.org
RByers has just created a new issue for https://github.com/w3c/pointerevents: == offsetX/offsetY is confusing for GetCoalescedEvents == See [this chromium bug](https://bugs.chromium.org/p/chromium/issues/detail?id=721485) and the [definition](https://drafts.csswg.org/cssom-view/#dom-mouseevent-offsetx) of `offsetX`/`offsetY`. Since an important use case of `GetCoalescedEvents` is to re-use (and share) existing code, perhaps we really should try harder to make these events look just like normal events? Eg. copy the `target`, and set the "dispatch flag" so that `offsetX`/`offsetY` get computed relative to the target? Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/209 using your GitHub account
Received on Friday, 12 May 2017 16:49:05 UTC