Skip to content
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 Report][3.7.0] Mount order of components of a VLayout inconsistent #20456

Closed
Joebayld opened this issue Sep 11, 2024 · 1 comment
Closed

Comments

@Joebayld
Copy link

Environment

Vuetify Version: 3.7.0
Last working version: 3.6.15
Vue Version: 3.5.4
Browsers: Chrome 128.0.0.0
OS: Mac OS 10.15.7

Steps to reproduce

  • Open the link and view the console
  • Toggle Vuetify versions between 3.6.15 and 3.7.0 while observing console

Expected Behavior

The mount order used to go from parent down to child, so the console would read:

Mounted Layout
Mounted Child

Actual Behavior

Since version 3.7.0, the mount order is from child up to parent. The console reads:

Mounted Child
Mounted Layout

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

I'm pretty sure this is related to #15229

The behavior obviously is different between the versions and this actually broke a feature of my app. I was relying on properties being set in the parent's onMounted call before the children get mounted. I can make either option work, but I'm not sure what is expected behavior in the lifecycle chain.

@KaelWD
Copy link
Member

KaelWD commented Sep 11, 2024

This is back to how it worked in 3.5, #15229 was reverted in 3.7 because suspense is still unstable and broken.

I'm not sure what is expected behavior in the lifecycle chain

child -> parent for synchronous components, parent -> child for async:
https://vuejs.org/api/composition-api-lifecycle#onmounted

@KaelWD KaelWD closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants