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 have a webapp with a lot of poppers in a calendar-view. Each calender-event can have its own popper. On logout, the calender gets destroyed and so do all the poppers. Now we get a performance issue, because of a lot of clearTimeout()'s. I found them in ngOnDestroy in popper-directive.ts:
I have a webapp with a lot of poppers in a calendar-view. Each calender-event can have its own popper. On logout, the calender gets destroyed and so do all the poppers. Now we get a performance issue, because of a lot of clearTimeout()'s. I found them in ngOnDestroy in popper-directive.ts:
ngx-popper/src/popper-directive.ts
Lines 238 to 239 in 5a8af28
We dont have a single popper with a delay - so these clearTimeout()'s are useless for us. My idea: A simple
instead of
Would fix it, right? But i‘m not sure if this has any side-effects for those who use delay on their poppers.
The text was updated successfully, but these errors were encountered: