 So, umm, we inadvertently broke `linear()`, `cubic-bezier()`, and `steps()` in certain cases in Chrome 128 š¬ Itās broken in the case where you have whitespace after the opening `(` Broken: `linear( 0, 1)` https://issues.chromium.org/issues/361652145 (Itās only the whitespace after the opening `(` causing issues here. All other whitespace does not affect things, as typically goes in CSS) 3 comments
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. UPDATE: The fixes got merged into the Chrome 128 branch, and are included in the upcoming 128.0.6613.133 build. (Sorry it took some time. There was some labelling mixup on the bug itself and therefore the automated system didnāt immediately pick it up for 128 inclusion) |
Gregory's Server
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.