This was supposedly fixed by at least Safari 14.1 (or earlier).