ugh, darn pre tags didn’t work for my html and i’m trying to fix it but it’s telling me that i have already posted the same code so i can’t make an update. if you can fix my post pleae do, also where is the option to delete my original posting of the topic?
thanks to @max for catching my use of a primitive when I should’ve been using an object $scope.data = {}; and ng-model=“data.query” as that did work and is considered a best practice.
i’m still getting the firing twice of my ng-click=“search()” when i output to the controller.
I’m using Icenium to do my mobile development and have pulled in all of your seed code and modified it from there. I have it set for Android v4.2 currently for testing. I haven’t tested it using webstorm + chrome but I will also do that as I didn’t think it would matter if I used Icenium but as you pointed out, maybe it does. I will let you know.
@adam it looks like it’s an issue with Icenium as I see the ng-click show my query value twice in the console but when I use brackets and chrome to run my app, it’s only showing one query via ng-click. thanks for that suggestion to look there as i didn’t think Icenium would’ve been the problem. I’ll take it up with them.
Also, if you could try the nightly build I made a small change to the tap/click feature, hopefully this solves your issue: http://code.ionicframework.com/#nightly
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.
I have this issue, ng-submit or ng-click fire twice, I’m using rc1, my IPAD 2 ios 7, and chrome (lastest osx). Any workaround? This two ways fires stsearch() twice.