[NickM]

This is a problem with the version of Webkit OW is using; it has the same problem. More recent Webkit builds rectify the problem and so the next sneakypeek should fix it as well.