Hi, as Brandon says, the bug was fixed for me and others at the time (or shortly after) with a patch.
It was a strange one, sort of a quasi Chrome/Wordpress bug/non-bug!
It was reported on my behalf to Chrome whose tech guys (I believe) recognised the ‘issue’ but said it’s not a bug with Chrome but admitted that it was only specific to their browser because of some formation/order of coding they use which processes typed text differently to other browsers.
Via its patch, WordPress changed the way some text was handled or something like that, which eradicated the problem.
So in layman’s terms I believe a change to WP or Chrome could have sorted it, I’m not sure if Chrome ever made any changes to ameliorate this ‘issue’ but WP did with its patch relatively quickly.
So, sorry for your problem but this one is resolved!