-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Closed
Closed
Copy link
Labels
❗ p4-importantPriority 4: this fixes bugs that violate documented behavior, or significantly improves perf.Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.🐞 bugSomething isn't workingSomething isn't workingscope: custom elements
Description
Vue version
3.5.3
Link to minimal reproduction
Steps to reproduce
- Create and define two custom components with
{shadowRoot: false}
and andonMounted
- Use one component inside each other:
<my-comp1>
<my-comp2>
<div>I'm not shown</div>
</my-comp2>
</my-comp1>
What is expected?
setup script and onMounted callback is called for components in hierarchical order:
my-comp1
my-comp2
<div>I'm not shown</div>
visible in dom.
When shadowRoot
is set to true
setup and onMounted callback are called in the correct order.
What is actually happening?
setup script and onMounted callback is called for components in following order:
my-comp2
my-comp1
<div>I'm not shown</div>
not visible in dom.
This deviates from standard lifecycle of vue components.
System Info
No response
Any additional comments?
No response
Metadata
Metadata
Assignees
Labels
❗ p4-importantPriority 4: this fixes bugs that violate documented behavior, or significantly improves perf.Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.🐞 bugSomething isn't workingSomething isn't workingscope: custom elements