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
{{ message }}
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.
i added ng-click-outside version ^3.2.0 to my project.
i have a component which is hidden with *ngIf.
i added (clickOutside)="close()" to the first element inside the component.
i am having the following issue:
in the parent component when i click on a link to display the child component (changes *ngIf from false to true) i see that the clickOutside event gets fired even before the child component itself is visible. and because when clickOutside is fired it raises a method that closes the child component - it disappears before it ever appears.
Perhaps the comportament is correct, @shahafal .
When click and the directive *ngIf remove the item, at the exact momment your action not is more in component. I solved with setTimeout(() => {my condition}, 10);
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
i added ng-click-outside version ^3.2.0 to my project.
i have a component which is hidden with *ngIf.
i added
(clickOutside)="close()"
to the first element inside the component.i am having the following issue:
in the parent component when i click on a link to display the child component (changes *ngIf from false to true) i see that the clickOutside event gets fired even before the child component itself is visible. and because when clickOutside is fired it raises a method that closes the child component - it disappears before it ever appears.
here is my code:
parent component:
child component:
child typescript class:
versions of packages i am using (from
ng --version
):The text was updated successfully, but these errors were encountered: