Just wrote a reply on another thread about the double click problem. I’m also experiencing it with Chrome 32.0.1700.107
For me, the tap simulation is artificially firing the click event and then the native click event kicks in, producing a double call on the callback defined in any ng-click.
Sorry for the misplaced post… Maybe I should copy it in this thread.