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:

http://blog.johnmckerrell.com/2007/03/07/problems-with-safar...

Basically if you are at or near 100% CPU, Safari’s HTML parser silently fails to parse your HTML.

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.

EDIT: formatting and cleanup