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)