> What I find really disconcerting about that is that there's this sort of implication there that Google would be willing to add a similar misfeature to their onscreen keyboards if they could get away with it.

Remember the old iPhone 'duck' autocorrect issue?