That happens to me all the time, so much so that I usually end up figuring out the problem that I wanted to ask of a SO or list post in crafting the minimum-replicable case for the post. It may also be some kind of event conflict between the <a> element containing the ng-click, and the ng-click itself.
e On Sat, May 31, 2014 at 8:30 AM, Chris Dieringer < [email protected]> wrote: > Hi Eric: > > Thanks for the willingness. In making a fiddle, apparently I convinced > myself otherwise. Working fiddle here: > > http://jsfiddle.net/cdaringe/FNky4/1/ > > Shoot. Must have been fighting some other issue! > > -Chris > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
