As an aside, have you considered using the ng-class directive? It's pretty handy for programmatically (and declaratively) manipulating classes on an element. It's not always the answer, but I keep finding neat uses for it.
e On Wed, Sep 17, 2014 at 8:16 AM, Sander Elias <[email protected]> wrote: > Hi Mark, > > The first one uses jQlite/jQuery, the second one is manipulation the DOM > through its native interface. > I can't explain why the first one would not work. If you want to know, > post an plunk showing the > problem, and I will find the issue for you. (The plunk needs to be > working!) > > Regards > Sander > > -- > 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.
