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
I think the first time of modal close will move the element to inner the div immediately through twitter-bootstrap (without removing the dom, just display: none) which does not trigger the onDestroy defined in lazyload-image.directive.ts unless url input
changed.
So the second time of modal open with the same image url will have to move the mouse/scroll to get view rendered.
ps: ngAfterContentInit is also not triggered by closing the modal
The text was updated successfully, but these errors were encountered:
There is no easy fix for this since it's not possible to watch for dom changes. The only way is to let ng-lazyload-image know when the images become visible (again). Take a look at this comment: #197 (comment)
So in your case you will need to emit an event when the modal was loaded. Do you think it is possible?
I think the first time of modal close will move the element to inner the div immediately through twitter-bootstrap (without removing the dom, just display: none) which does not trigger the onDestroy defined in lazyload-image.directive.ts unless url input
changed.
So the second time of modal open with the same image url will have to move the mouse/scroll to get view rendered.
ps: ngAfterContentInit is also not triggered by closing the modal
The text was updated successfully, but these errors were encountered: