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
Hello.
I'm using some animations from Angular's platform-browser/animations package.
The problem is that ngx-masonry removes an element from DOM on ngOnDestroy hook by default.
Reasons for that are obvious of course.
But in that case i can't use any animations on leave because Angular removes HTMLElements after animation's (*.done) hook and that makes a strange effect when masonry grid is disappearing directly five seconds before than the main component does.
Also here is no any option in the config to prevent destroying right after ngOnDestroy.
Hi, thank you for reporting the issue. Unfortunately, I didn't find a way to resolve this, but I believe you can work around this by adding the animation to the component itself. Feel free to let me know if you have any idea about solving this problem.
Hello.
I'm using some animations from Angular's
platform-browser/animations
package.The problem is that ngx-masonry removes an element from DOM on
ngOnDestroy
hook by default.Reasons for that are obvious of course.
But in that case i can't use any animations on leave because Angular removes HTMLElements after animation's (*.done) hook and that makes a strange effect when masonry grid is disappearing directly five seconds before than the main component does.
Also here is no any option in the config to prevent destroying right after
ngOnDestroy
.I mean:
ngx-masonry/src/lib/ngx-masonry.directive.ts
Lines 60 to 65 in 9c616d8
The text was updated successfully, but these errors were encountered: