-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
Tabs component, ionViewWillEnter is not called on the active Tab, just the page holding the Tabs when doing nav back. #9787
Comments
I can confirm that it's still an issue in Ionic 2.1.0. |
I think this is not just the tabs but happening to any nested nav. The ionViewWillEnter is called on the page that is directly under the nav that is going through a transition, but if that page contained a child nav, its active page's ionViewWillEnter does not get called. |
Updating the issue. I'm navigating from ' TemplatePage' that is in tab navigation to another page using |
The same problem here. |
is this fixed? |
I have the same problem here, but I can get a workaround using:
|
to
automatically "ionViewWillEnter" starts firing after leave TabsPage and enter on it again |
This issue has been automatically identified as an Ionic 3 issue. We recently moved Ionic 3 to its own repository. I am moving this issue to the repository for Ionic 3. Please track this issue over there. If I've made a mistake, and if this issue is still relevant to Ionic 4, please let the Ionic Framework team know! Thank you for using Ionic! |
Issue moved to: ionic-team/ionic-v3#159 |
Ionic version:
[ ] 1.x
[x] 2.x
I'm submitting a ...
[x] bug report
[ ] feature request
Current behavior:
When navigating out of a page with a Tabs component and coming back, the ionViewWillEnter is called on the page holding the tabs component, but not on the active tab.
Expected behavior:
This event should probably be fired on the active tab.
Steps to reproduce:
this.app.getRootNav().push(SomeOtherPage);
Sorry about not creating a Plunker, I am really in a rush this month.
Temporary work around
In the parent page that holds the Tabs component:
In the child page (a Tab), I added this:
The text was updated successfully, but these errors were encountered: