- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jul 2019 23:35:42 +0000
- To: public-pointer-events@w3.org
patrickhlauke has just created a new issue for https://github.com/w3c/pointerevents: == Expand note about `click` / `contextmenu` == Based on questions/conversations with developers (e.g. a while back on twitter with @jakearchibald), make it clearer in https://w3c.github.io/pointerevents/#compatibility-mapping-with-mouse-events that it's still up to the UA to determine whether or not a `click` or `contextmenu` is fired. For instance, on a touch interface, UAs may decide *not* to fire a `click` in response to a second finger tapping the screen if there's already a finger touching the display. Or they may omit a final `click` after a "dirty" tap that involved too much movement (the UA doesn't think the user intended to activate a button or link or just generally "click" anything, so after `pointerup`/`pointerleave` there's no `click` at the end). This is outside of the scope of the PE spec per se, but should be made clear in the informative notes (and perhaps even noted somewhere in the "default actions" part) Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/292 using your GitHub account
Received on Thursday, 11 July 2019 23:35:44 UTC