3 ms·
The Chromium bug describes the root cause, which is a fixed schedule interval for CSS animations: > The JS implementation uses an interval of 500ms between upd
by ohitsdom 10y ago
The Chromium bug describes the root cause, which is a fixed schedule interval for CSS animations:
> The JS implementation uses an interval of 500ms between updates while native animations will be updating at 60Hz. At the moment we're not smart enough to deschedule ourselves during animations with step timing functions.
https://bugs.chromium.org/p/chromium/issues/detail?id=500259 https://bugs.chromium.org/p/chromium/issues/detail?id=500259
- petters 10y agoThe fact that animating a cursor at 60Hz requires non-neglible CPU is still a little sad.