Thanks for firguing that out, Isaac! To me this makes it sound like a Webkit bug (Webkit is the rendering engine behind Safari and Chrome). I was unable to find a specific related bug report, but I suspect that there's nothing that we'll be able to do.
↧