The bug is already fixed in Chrome Canary (version...

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.

Like 26 August at 17:24 | Open on front-end.social

1 comment

Bramus

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)

6 September at 9:35 | Open on front-end.social

Go Up