I'm observing the same behavior now in Safari 16.3. What's weird is that it works for me fine in 16.1. @lyyoo9 have you been able to find a solution or a workaround?