-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong rendering of Angular component (*ngIf) #13181
Comments
Automention: Hey @MaximSagan @kroeder, you've been tagged! Can you give a hand here? |
Should be fixed by #12382. I patched my node_modules to set the props in I couldn't reproduce it in chrome. Your second screenshot looks like you are using Firefox, so I tried it and was able to reproduce the issue. The |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Describe the bug
A simple component with an
*ngIf
has unexpected behaviour. You can reproduce the issue from this project.Lets say I create a wrapper over ionic button component.
The issue is with
isLoading
control. The component should display one spinner, but instead, it shows two for some reason.To Reproduce
Playaround with
isLoading
control of ion-button-wrapper of this projectExpected behavior
There should be a single spinner spinning in the button.
Screenshots
The text was updated successfully, but these errors were encountered: