- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2016 16:14:38 +0000
- To: public-pointer-events@w3.org
In the call today @NavidZ raised a good question: what should the `PointerEvent` properties be for these events? Using the values from the previous pointer event could make sense, but would be problematic - eg. the client/page co-ordinates may be inconsistent with the current scroll offset (which may have changed since the last event was generated). Options I see: 1. All pointer properties other than `pointerType` and `pointerId` always have their default value for `gotpointercapture` and `lostpointercapture`. This is simplest and easiest to explain, I'm not sure there's any scenario where you really want co-ordinates in one such listener. But this might be breaking or unnecessarily strict. 2. `got/lostpointercapture` events generated as a direct result of another pointer event inherit the pointer properties from it. 3. Most pointer properties are copied directly from the last pointer event for that pointerType/id, but properties that reflect the DOM state (eg. `page` co-ordinates) are re-computed in the context of the current DOM state. Next step is to better understand exactly what Edge is doing for these cases. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/32#issuecomment-232406230 using your GitHub account
Received on Wednesday, 13 July 2016 16:14:45 UTC