As far as I can tell the bug affects all 2.x stock browsers (just ran it on an emulator to be sure). My 4.2 phone works correctly. One of those links also pointed to Chrome 1-10 and older Safaris / IE as problematic too