- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Jul 2021 17:53:50 +0000
- To: public-pointer-events@w3.org
The following commits were just pushed by patrickhlauke to https://github.com/w3c/pointerevents: * Expand explanation for non-coalesced events (#379) * Expand explanation for non-coalesced events - a user agents may coalesce events not just if the position is updated, but any of the attributes (as it's not just position changes that can result in an overwhelmingly large number of events) - tweaked the matching sentence in the `pointerrawupdate` slightly, to use `pointer's attributes` rather than the awkward sounding `pointing device attributes` Closes https://github.com/w3c/pointerevents/issues/375 * Tweak following sentence of the coalesced events description as well. * Further expand as this also applies to `pointerrawupdate` events * Explain which properties usually get coalesced - includes glossary definition for discrete and coalesced properties * Exclude discrete keyboard modifier properties from needing to fire pointermove * Replace the discrete/continuous concept with "measuable properties" instead due to the fact that `tiltX`, `tiltY`, `twist` being `long` properties would count as discrete under the general definition. * Remove mention of *key properties in the coalesced events section altogether no need to mention them, as they don't lead to pointer events firing anyway * Missing space * Change "will" to "may" * Add "continuous" to further clarify the measurable properties concept by Patrick H. Lauke https://github.com/w3c/pointerevents/commit/11dd1cdf6258b71fe9b8d6be5283f451e38e5deb -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 July 2021 17:55:37 UTC