-
-
Notifications
You must be signed in to change notification settings - Fork 241
[Angular 10] Using *ngIf breaks layout order #2249
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
Comments
This is also a bug with Angular 9, see here: #2176 |
Same problem here. Appeared after upgrade to Angular 10 and NS 7.0. |
This issue is now fixed with @NativeScript/angular 10.1.3 published now 👍 |
Hi @NathanWalker. I'm facing this issue in a large messaging application. I can't update to Angular 10 yet because there are plugins with no NativeScript 7 compatibility. Shouldn't this be the case to have a fix for this issues also available in the @nativescript/angular 9 package? |
@rickwalking can you try this release: https://github.com/edusperoni/nativescript-angular/releases/tag/8.21.2 ? |
Environment
Describe the bug
Using *ngIf over an element/component breaks layout order unless the element/component is wrapped in another layout.
To Reproduce
just try:
Expected behavior
First label
should be rendered beforeSecond label
.Sample project
https://github.com/mohammadrafigh/dynamic-component-issue
Additional context
I'm not sure if it just happens with StackLayout or not but as a workaround wrapping
First label
like this fixes the order problem:If it helps, the problem occurred after upgrading to Angular 10.0.0 but since the core module was in "rc" I thought this might be a known issue and would be fixed in final release, So this may be an inconsistency problem with Angular rendering behavior and Nativescript runtime.
The text was updated successfully, but these errors were encountered: