-
Notifications
You must be signed in to change notification settings - Fork 264
How should we handle components with fragments? #19
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
Comments
<template>
<div id="foo" />
<div id="bar" />
</template>
I think we drop |
|
Did some more digging: I could not find a way to fetch all the children from the ComponentPublicInstance we have access to. See https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentProxy.ts#L78 |
Seems like you found something since making this comment - are we able to have find work on components with multiple root nodes now? |
As Vue 3 now allows having components with multiple root components, aka fragments, we need to figure out what to do with methods like:
Of course some of these will depend on the outcome of #17
I am testing some things out locally, and
vm.$el
does not work with multi root components.The text was updated successfully, but these errors were encountered: