Re: [pointerevents] Click event while a pointer event is captured

It seems we have all agreed that the nearest common ancestor of 
pointerdown & pointerup should receive the click event, right?

We shouldn't fire click for non-primary buttons, so we can restrict 
the events to primary buttons only ("pointerdown with button=0" and 
"pointerup with button=0" instead). This would cover the chorded 
buttons case but won't fire a click when the primary button doesn't 
cause pointerdown and/or pointerup.

I think this is fine. Alternatively, we can somehow include "mousemove
 with button=0" to fire a click event even on chorded primary buttons.
 IMO, this would make the spec a bit counter-intuitive w.r.t. the UI 
event spec, which perhaps doesn't make sense for this rare corner 
case.


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

Received on Wednesday, 8 June 2016 17:40:05 UTC