You can see my comment on this commit here to explain the problem with that commit further. But, I truly don't understand how in an attempt to bust the redundant, original/"ghost click" click event (because it's being done faster than the original thanks to this wonderful work) we would also want to prevent the very likely intended behavior of also focusing a clicked focusable element. After all, it isn't as if this focusing behavior is also redundant; ngTouch's ngClick doesn't also focus the element if focusable when it triggers the click event. But before I contribute either a removal of this blurring "feature", or the addition of a speedier focusing feature, do you all agree that something must be done?

Because FYI, (and I'm sure I'm not the only one) my organization is relying my own copy of Angular just to remove this one line of code. (...which happened to break the login for my company's site, as well as all other inputs in all other dialogs, and even gave pause to my CTO that we should even be utilizing Angular to the extent we are considering this bug was because of migrating to 1.4.0 - though technically a minor release, it's hardly a minor release)