You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I log ngAfterContentInit, I see that the function is called only for the initialy displayed elements. When I move the mouse to reach other elements, the ngAfterContentInit is called on more time for the first next element but that’s it, no more call no matter how long is the list. It’s a problem because I need to execute some code for each element in the list.
I think it's bug or I don't understand this behavior...
The text was updated successfully, but these errors were encountered:
This is due to the view recycling done by the native views. You can use ngOnChanges() callback if you want to get notified about views data binding has been changed. (Change detection is triggered by the list view component on the views created from the template(s)).
Hi!
I found a strange behavior with ListView I can't understand it...
If I have created a very basic list:
With a simple component as template:
When I log ngAfterContentInit, I see that the function is called only for the initialy displayed elements. When I move the mouse to reach other elements, the ngAfterContentInit is called on more time for the first next element but that’s it, no more call no matter how long is the list. It’s a problem because I need to execute some code for each element in the list.
I think it's bug or I don't understand this behavior...
The text was updated successfully, but these errors were encountered: