And the ng disabled does the toggling as the condition result Changes. Is that correct?
> On May 19, 2017, at 8:52 PM, Sander Elias <[email protected]> wrote: > > Hi Reza, > > ngIf will take the button out when it's condition is not met. That's probably > not what you want to do. Most of the time, disabling it is the right thing to > do. > > <button ng-disabled="!$ctrl.SomeCondition">Button</button> > > If you really need to make the button go away, replace the ngDisabled with > ngIf > > Regards > Sander > -- > You received this message because you are subscribed to a topic in the Google > Groups "Angular and AngularJS discussion" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/angular/PB8mtFCVxKs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://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 "Angular and AngularJS discussion" 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
