[pointerevents] Attributes of lost/gotpointercapture events fired immediately on set/release capture

mustaqahmed has just created a new issue for 
https://github.com/w3c/pointerevents:

== Attributes of lost/gotpointercapture events fired immediately on 
set/release capture ==
This is blocked on #32. I am creating this new issue because @NavidZ's
 
[comment](https://github.com/w3c/pointerevents/issues/32#issuecomment-232687047)
 there needs a bit more attention.

Since Edge is not delaying 
<code>lostpointercapture</code>/<code>gotpointercapture</code> in some
 cases and Chrome will be following a similar approach soon, the 
attribute values for, say, <code>button</code> or 
<code>pressure</code> seems to become irrelevant for these 
<code>lostpointercapture</code> and <code>gotpointercapture</code> 
events (i.e. for the ones fired immediately after a call to 
<code>setPointerCapture</code> or <code>releasePointerCapture</code>) 
because there is no hardware events to provide us the values here.

I see three possible ways to spec this:
A. Don't say anything, and expect UAs to pick up a consistent behavior
 (or expect developers rely on only the meaningful attributes).
B. These events set only the meaningful attributes (only 
<code>pointerId</code>?). All other attributes are either default or 
unknown.
C. These events always carry the attributes of the last known event 
for the <code>pointerId</code>, for both immediate firing and lazy 
firing in response to a real event.

Comments?

Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/113 using your GitHub 
account

Received on Thursday, 21 July 2016 16:40:09 UTC