You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I just saw the presentation at https://youtu.be/mDdgfyRB5kg and are confused to what happens when multiple high priority messages are dispatched. Are they queued or dropped?
For touch events, the input rate can be extremely high and we might only need the latest position. Is this handled by this proposal?
The text was updated successfully, but these errors were encountered:
Sorry for the delay.
Posted tasks are never dropped, and will be queued.
Regarding input, this proposal does not change input handling and currently no changes are proposed to input event handlers.
Note that chrome coalesces continuous input sources (eg. mouse wheel) and aligns them before requestAnimationFrame.
Hi @NE-SmallTown: Apologies, this got lost in the shuffle. For more info, I found a chromestatus entry about this. It has links to a design doc and old discussion thread.
Closing this issue as the APIs we're pursuing have evolved a bit. Please feel free to file new issues against the recently updated explainers, in particular the postTask explaner.
Hi. I just saw the presentation at https://youtu.be/mDdgfyRB5kg and are confused to what happens when multiple high priority messages are dispatched. Are they queued or dropped?
For touch events, the input rate can be extremely high and we might only need the latest position. Is this handled by this proposal?
The text was updated successfully, but these errors were encountered: