It was a bug in WebKit that WebKit had to fix (and as you know, Safari takes a long time getting those fixes into consumer's hands).
Testing in non-Chrome browsers should identify anything like this before stuff ships. It is legitimately not hard to do.
If it even does.