Do user agents only coalesce pointermove events relating to changes in position? #375
Comments
- auser 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 #375
- 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 #375
|
Just looking at the implementation, Gecko may coalesce also when things like tilt or twist or pressure changes. |
|
I would expect that every non-discrete field could /should be coalesced. I.e. in your original post the only thing I wouldn't expect to get coalesced would be the button state since that changes discretely. I believe blink does this by virtue of the button state change also causing discrete events to fire which forces us to flush the current coalesced event out first. |
|
Discussed today to update to |
|
may need glossary entry as well for discrete/non-discrete properties (in former also include |
|
Added the proposed update to the wording, plus a glossary definition for "discrete and coalesced properties", to #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 #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
https://w3c.github.io/pointerevents/#coalesced-events states that
Does this really only apply to position updates? Or do changes in other attributes ("i.e. button state, coordinates, pressure, tangential pressure, tilt, twist, or contact geometry", to borrow from the
pointerrawupdatedescription) also get coalesced (and the non-coalesced events would have the more granular changes from those attributes)?The text was updated successfully, but these errors were encountered: