Troy Morehouse
Troy Morehouse
That would cause the same Vue vNodes to appear in multiple spots in the document, which is a Vue no-no (no duplicate VNodes)
That would be true.. but you would have to ensure that it only works when the default slot is a function
This would be because the child `` is no longer nested within the parent `` when portalled: the parent hierarchy changes (https://portal-vue.linusb.org/guide/caveats.html#known-caveats) if your `` is not rendered within your...
One workaround would be to use named ``s, and set the "child" route to be targeted to that name view (https://router.vuejs.org/guide/essentials/named-views.html#named-views)
There is a way to force a particular parent on a component... it requires manual mounting though (note I haven't tested this example code, but I have done similar for...
what about a new event `targets-changed` (or some better name)?
If the dialog has a single root element, wouldn't the `slim` option make the inner content the root element (this.$el) and the class would be placed in it? or is...
Just realized that slim is only applicable to `disabled` mode. I also tried setting portal's tag to `transition` (which has the nice effect of rendering `` instead of a visually...
@LinusBorg you could prep people with a new element name (i.e. ``) while still being backwards compatible (by providing `` as well): ```js function install(Vue: VueConstructor, options: PluginOptions = {})...
And then in a major release, drop the older deprecated ``