Re: [pointerevents] Pen Button Events (#290)

I might still be a little confused what the problem is referring to. But this issue #134 might also be related. I feel like I might get the problem more during the call when we discuss this issue.

However as a side node, Assuming we go with eraser button route in #134, the way it seems it should work is that when you are hovering and pressing the eraser button it should send a pointerdown with eraser button and then if you touch the screen, should send a pointermove this time with `button=left` and `buttons=eraser | left`. I guess this is because we agreed that stylus touching the screen is the left button. This is under the assumption that we are getting the eraser button change while hovering on the platform. If we don't then when the stylus touches the screen while the eraser button is depressed we need to send a pointerdown but the question remains about button and what we should set it to. As essentially in this case we have both left (i.e. touching the screen) and eraser button changed at the same time from the UA perspective on a platform that doesn't support hover. The same scenario happens more or less for an inverted stylus. 

Regardless, what I'm suggesting is to not based any decision on what Chromium does today. It might just be a bug or a scenario that we didn't think about it before. I know it might not very well thought and we have all these cases like the ones above that we just implemented something that sounded right but not yet fully decided and clear in the spec. 



-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/290#issuecomment-505852576 using your GitHub account

Received on Wednesday, 26 June 2019 12:26:12 UTC