This is probably caused by a bug in Safari. I had the same issue a few times on macOS Monterey, but recent Safari versions seem to be less prone to it.
A possible fix is described here:
Make sure to restart Safari after running the command.
This is probably caused by a bug in Safari. I had the same issue a few times on macOS Monterey, but recent Safari versions seem to be less prone to it.
A possible fix is described here:
Make sure to restart Safari after running the command.