A huge blunder or a yet-to-be tweaked nuance of the Webkit engine? Seems to me that a huge blunder would entail a very difficult to address issue. I'll chalk this up as a minor blunder.
It really seems like one of those after release patch items. Something that OS X would have in a 0.0.1 update. It is iPad 3 generation specific and they didn't do a specific release update this time so that might make it a patch item.