- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jun 2019 19:25:39 +0000
- To: public-pointer-events@w3.org
@annevk That part was intentional on the spec. Right now FF and Chromium do different algorithms and heuristics for coalescing. We wanted to first try and expose those events using this API. Then we can iterate later on different spec to land on a standard behavior on what and how to coalesce events. In that sense we wanted to leave this to the UA behavior for the current version. There is a normative text that says the logic for coalescing and what not is "based on UA decision". -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/280#issuecomment-500987408 using your GitHub account
Received on Tuesday, 11 June 2019 19:25:41 UTC