New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attributes of lost/gotpointercapture events fired immediately on set/release capture #113

Closed
mustaqahmed opened this Issue Jul 21, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@mustaqahmed
Contributor

mustaqahmed commented Jul 21, 2016

This is blocked on #32. I am creating this new issue because @NavidZ's comment there needs a bit more attention.

Since Edge is not delaying lostpointercapture/gotpointercapture in some cases and Chrome will be following a similar approach soon, the attribute values for, say, button or pressure seems to become irrelevant for these lostpointercapture and gotpointercapture events (i.e. for the ones fired immediately after a call to setPointerCapture or releasePointerCapture) 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 pointerId?). All other attributes are either default or unknown.
C. These events always carry the attributes of the last known event for the pointerId, for both immediate firing and lazy firing in response to a real event.

Comments?

@RByers

This comment has been minimized.

Show comment
Hide comment
@RByers

RByers Jul 27, 2016

Contributor

Discussed this at the hackathon. We agree it probably doesn't really matter, but assuming we go with the delayed design (#32) then the simplest / least surprising thing to do is to just copy all the properties from the pointer event that triggered the sending of the lost/got event. There may still be some cases where a pointercancel event has default values, and those get copied into the lostpointercapture but that's fine.

Thoughts?

Contributor

RByers commented Jul 27, 2016

Discussed this at the hackathon. We agree it probably doesn't really matter, but assuming we go with the delayed design (#32) then the simplest / least surprising thing to do is to just copy all the properties from the pointer event that triggered the sending of the lost/got event. There may still be some cases where a pointercancel event has default values, and those get copied into the lostpointercapture but that's fine.

Thoughts?

@NavidZ

This comment has been minimized.

Show comment
Hide comment
@NavidZ

NavidZ Jul 28, 2016

Member

Sounds good. Do you like to explicitly call that out about got/lostpointercapture in the spec that their attributes need to be the same as the PointerEvent that caused them to be processed? Note that currently Edge doesn't do that for lostpointercapture. Were the Edge folks okay with this to change lostpointercapture?

Member

NavidZ commented Jul 28, 2016

Sounds good. Do you like to explicitly call that out about got/lostpointercapture in the spec that their attributes need to be the same as the PointerEvent that caused them to be processed? Note that currently Edge doesn't do that for lostpointercapture. Were the Edge folks okay with this to change lostpointercapture?

@RByers

This comment has been minimized.

Show comment
Hide comment
@RByers

RByers Jul 28, 2016

Contributor

Yes, I think we should call this out in the spec and include testing for it. Edge devs indicated it was a reasonable change for them to make.

Contributor

RByers commented Jul 28, 2016

Yes, I think we should call this out in the spec and include testing for it. Edge devs indicated it was a reasonable change for them to make.

@teddink

This comment has been minimized.

Show comment
Hide comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment