Thought I was going crazy. I tracked it to jquery. Then google confirmed it http://bugs.jquery.com/ticket/13239
Oh! That's nasty.
It also seems to affect Chrome and Safari on the PC.
And, come to think of it, I've been experiencing some weird behaviour from one of my Chrome extensions in conjunction with jQuery lately.
Maybe this has got something to do with it.
Anyway, as this is a regression from 1.8.3, you can just drop back to that version by way of a workaround until they fix the problem.
Or, if you absolutely need to use the latest version, just do:
Thanks Pullo. I do have to use it. One of the plugins needed it. Everything works now though with it. Pretty sure that would only affect ie anyway. They'll fix it I'm sure in the next release. That is pretty nasty though. That could do a lot of damage to sites. I was seeing it in my iPhone source and just scratching my head. Ben doing that a lot on this site.
Yeah, a lot of the time I just include jQuery latest for development purposes, but then forget to specify an exact version on the live site.
This is a great example of why that is a bad idea.
The new site's looking god by the way
jQuery 1.9.1 was released yesterday, and ticket #13089 has been listed as being fixed.