Skip to content

Conversation

@AlessandroDG
Copy link

@AlessandroDG AlessandroDG commented Jun 2, 2017

This should fix #113
Some may find this useful because sometimes ng-hide/ng-show cannot be replaced by ng-if.
ng-if renders the element (and executes the controller) every time its value goes from false to true, and in certain cases that is inconvenient.

In my specific case I couldn't use ng-if because I needed the controller of the element to be executed even though the element itself would not be in the viewport yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issues with ng-show/ng-hide

1 participant