It was a safari/webkit issue.

The latest 26.1 beta from 22 September has fixed the issue. Now we just need to wait for it to be released or a patch to go before that.