Same behavior. The workaround indicated by XSalvador works. I filed to the feedback assistant: FB12399192 Safari Version 16.6 (18615.3.3.11.1)