Thanks for the report! Unfortunately, as you can see in the image it's currently a known issue with Webkit, specific to Apple. As such there's not much that anyone can do until they patch the issue on their side.
