@core I've seen the issue with Chrome. It's a bug in Chrome that messes with TextExpander. There's also a FF bug: http://t.co/K7RsVOZz

8:43am April 9th 2012 via TweetDeck in reply to