Disabled teleport inside fragment causes SSR hydration mismatches
Vue version
3.2.37
Link to minimal reproduction
Steps to reproduce
N/A
What is expected?
No warnings
What is actually happening?
Hydration completed but contains mismatches
with no information about where they are.
This newly inserted anchor can then cause Hydration children mismatch in <div>: server rendered element contains more child nodes than client vdom
in its parent element.
System Info
No response
Any additional comments?
Having a separate warning for "fragment didn't hydrate successfully" would be nice too.
b60cff052c880b2965d06007f0ec4d0349ab47c0 didn't account for disabled teleport, nextNode
is the teleport content instead of <!--teleport end-->