-
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: Teleported components are not unmounted in Vue #26644
Comments
@raymer thanks for reporting this issue! I'm able to reproduce and have narrowed it to the changes I recently made here: #26543. I'll log this as a bug and dig deeper into why there is an objective difference between the filter and splice usage and how to solve the original bug and restore the regressed behavior. |
@raymer can you test with this dev-build and let me know if you run into issues?
|
@sean-perkins that looks like the fix. Didn't notice any other issues 👍 |
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. |
Prerequisites
Ionic Framework Version
Current Behavior
As of 6.4.2, when modals are opened (at least via modalController) they aren't unmounted on dismiss, causing stale data on creation of the modal again. (All previous refs, etc still have their data from last time the modal was created)
Expected Behavior
On dismiss, modals should unmount, causing all refs and other data to clear.
Steps to Reproduce
Code Reproduction URL
https://github.com/raymer/ionic-modal-bug
Ionic Info
Ionic:
Ionic CLI : 5.4.16 (C:\Users\rayme\AppData\Roaming\npm\node_modules\ionic)
Ionic Framework : @ionic/vue 6.4.2
Capacitor:
Capacitor CLI : 4.6.1
@capacitor/core : 3.9.0
Utility:
cordova-res : not installed
native-run : 1.7.1
System:
NodeJS : v18.12.1 (C:\Program Files\nodejs\node.exe)
npm : 8.19.2
OS : Windows 10
Additional Information
No response
The text was updated successfully, but these errors were encountered: