Thanks for the test scene. I can confirm this bug still exist on Safari 16.1 on Ventura 13.1.1 on M1 MBA