-
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
bug: @ionic/vue uses page transitions for Android, but not for iOS #19042
Comments
Additionally, setting |
@michaeltintiuc is there anything else I can provide to help triage? I've been trying to debug the issue myself, but I'm not expert at either vue or ionic. Digging into |
After digging through tons of examples, I noticed some with
After wrapping all of my pages in |
That's a great find, I've never tried without |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
Ionic version: 4 (
@ionic/vue@0.0.9
)Current behavior: An app using
IonicVueRouter
will correctly follow Android transitions, but will ignore iOS transitions. Navigating in iOS sometimes leaves a "ghost" of the previous page's components as they are kept around for the transition animation that never happens.iOS:
![ionic-vue-ios](https://user-images.githubusercontent.com/364501/62674137-1bc64d80-b96f-11e9-815a-fa633d6d3212.gif)
Android:
![ionic-vue-android](https://user-images.githubusercontent.com/364501/62674138-1bc64d80-b96f-11e9-802a-1b75416e051f.gif)
Expected behavior: Navigating through the same app in Android and iOS should always include page transitions, regardless of client platform.
Steps to reproduce: Run any
@ionic/vue
app in chrome with emulation on. Toggle between iPhone 6/7/8 and Nexus 5X, refreshing between each toggle. Navigate through the pages in the app and observe animations on Android but not on iOS.Ionic info:
The text was updated successfully, but these errors were encountered: