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 was archived by the owner on Apr 12, 2024. It is now read-only.
I think I found a bug with ng-if directive. I can not manage to reproduce it in a js fiddle. The bug is within a big project. I tried to simplify it but there is no bug wher I do so...
The contract status is modified by a another event in a contract controller.
I think we can assume that if the first line shows false, then the div should not be in the dom (the test is the same). From time to time (1 of 3 more or less), I have that :
I'm sorry I can not reproduce that in a fiddle, I know my report is not being very helpfull but I just wanted to let you know.
Anyway, thanks for this awesome framework! Best Regards,
Ruben
The text was updated successfully, but these errors were encountered:
@ruben-podadera without a way to reproduce this, then there is very little that can be done. What version of angular are you using? The closes report I can think about is #4930 that was fixed quite a few month back
Hi,
I think I found a bug with ng-if directive. I can not manage to reproduce it in a js fiddle. The bug is within a big project. I tried to simplify it but there is no bug wher I do so...
This piece of code is in a directive template
The contract status is modified by a another event in a contract controller.
I think we can assume that if the first line shows false, then the div should not be in the dom (the test is the same). From time to time (1 of 3 more or less), I have that :
I'm sorry I can not reproduce that in a fiddle, I know my report is not being very helpfull but I just wanted to let you know.
Anyway, thanks for this awesome framework! Best Regards,
Ruben
The text was updated successfully, but these errors were encountered: