Thank you Sander. I will avoid the usage of ng-if in such conditions.
The code snippet you provided was really great and helpful. Thank you again for taking an effort and providing solution to my problem, I highly appreciate it. - *Anurag*. On Thursday, March 26, 2015 at 11:59:22 AM UTC+5:30, Sander Elias wrote: > > Hi Anurag, > > Short answer: No. > > Somewhat longer answer: Actually the ng-show is a better solution if you > just want to show/hide a single/few element(s). ngIf takes it out of the > DOM (which is the reason you can't clear on un-checking, The entire element > including all its sub components/directives are pulled from the DOM, code > that isn't there, can't be run) This inserting and pulling is an very > costly operation, and should be used with care. ngShow and ngHide are much > more suitable for this kind of thing. they just show/hide the DOM without > changing anything. > Another thing, ngIf creates a new scope, which can threw you off if you > are not aware of that. > > 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.
