To see how far this extends, I queried the HTTP archive.
Out of the 559 million “root pages” in the set, about 6k are affected by this – mainly in their usage of `cubic-bezier()`.
While this is very unfortunate, I believe the number of affected sites seems quite reasonable.
At worst the effects on those sites will run using a `linear` timing, instead of the custom one.
The fix is easy too: remove the whitespace.
The bug is already fixed in Chrome Canary (version 130) and backmerges have been requested for 129 (beta) and 128 (stable).
EDIT: the backmerge wheels are turning. Looks like we'd be able to get this fixed in 128 as well.