Are high priority messages queued or dropped?
dotnetCarpenter opened this issue · 3 comments
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?
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.
Note that chrome coalesces continuous input sources (eg. mouse wheel) and aligns them before requestAnimationFrame.
Could you give more details about this?
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.