demo · v130

Ink-trail clinic

expectedImprovement was removed in Chrome 130 because authors used it as a knob to chase a target latency — which is exactly what the OS already does behind the scenes. Pick the symptom you're seeing in your ink-trail app, get a diagnosis, then see the before/after code. Live ink canvas at the bottom verifies the recommended replacement still gives smooth strokes.

presenting symptom

diagnosis

before (Chrome ≤ 129)


          

          

            
after (Chrome 130+)

            

          

        

      

    


    
live verification

    
Use a pen or finger on the canvas. The trail is drawn using the recommended Chrome 130 pattern: subscribe to pointerrawupdate + requestAnimationFrame for the on-screen path, and use the bare updateInkTrailStartPoint(event, style) call (no third argument) for the OS-delegated low-latency continuation. The continuation works whether or not expectedImprovement exists on the presenter.

    

    

      
      
    

  


  

    
see also