Enable web applications to describe the last input pointer with sufficient detail so that the browser can present the segments of the ink trail for input that has been delivered, but not yet rendered (the pointer trail).


Achieving low latency is critical for delivering great inking experiences on the Web. Ink on the Web is generally produced by consuming PointerEvents and rendering strokes to the application view. When desynchronized canvas is used to improve inking performance, there is no guarantee that the "dried ink" (previously rendered) content shows up in the same frame as the "wet ink" stoke just received. This can end up producing one frame with no ink content, or one frame where both wet and dry ink are visible, which results in a visual artifact of a flash of darker for non-opaque strokes. (See explainer for more comprehensive motivation.)


Status in Chromium


No active development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Search tags

ink, wet, dry, pointer, stroke, delegated, trail, low, latency,

Last updated on 2021-04-19