What makes it really bad is that there is also this bug in mobile WebKit from four years ago that nobody has ever gotten around to fixing:<p><a href="http://blog.johnmckerrell.com/2007/03/07/problems-with-safari-and-innerhtml" rel="nofollow">http://blog.johnmckerrell.com/2007/03/07/problems-with-safar...</a><p>Basically if you are at or near 100% CPU, Safari’s HTML parser silently fails to parse your HTML.<p>Additionally, we have found this is not limited to the innerHTML property; we have observed the problem to happen with the W3C recommended method Range.createContextualFragment.<p>EDIT: formatting and cleanup
My own PhoneGap-based iPad app is going really well so far, practically indistinguishable from native, but for one thing: WebKit refuses to let you have manual control over hiding and showing keyboards. (I tried filing a bug, and it was closed as "works as intended".)<p>This makes me feel like I have one hand tied behind by back when creating UI flow, and it's maddening.