Hey there @bweinstein, circling back on this issue, sorry for the delay, I appreciate your following up on this. However, I've run the my test again both via the code sample I uploaded for the feedback ticket, as well as with my company's project. In both cases I can still reproduce this issue. So I'm afraid it's not fixed, at least given my current environment. I'm on Ventura running Safari 16.1. Please advise!

I've not sure if this test fix is still live in Safari Technology Preview-- but I'm still experiencing this problem, tested on version 161.

Great, this is the workaround I've planned on using. Glad this will get fixed.