-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
page-router-outlet won't render if it's wrapped in an *ngIf that was initially false #1407
Comments
To me it now looks like a Nativescript 5.2, NS-angular 7.2.3 |
@daveware-nv The |
The problem still presents itself if you do as follows:
The page router is wrapped in a layout and has no siblings, but it will never display. |
@daveware-nv Yes, it doesn't work with *ngIf at the moment, hence the issue. I was talking more about the |
This issue mentions |
Hi, everyone. I still can catch this problem on ios, on android this work correctly :( |
See this playground example:
https://play.nativescript.org/?template=play-ng&id=m8kxO1&v=2
The property
a
is initiallyfalse
, then set totrue
in the next tick. The Label updates correctly to reflect this, but the page content never shows up.If you change the code to make
a
saytrue
initially, it renders as expected.Both iOS and Android, all latest versions.
The text was updated successfully, but these errors were encountered: