@Gargron Weird, probably a bug in Safari indeed.

Well not really a problem of course. I was just wondering how that happened.