Thorsten Lünborg

I see. The issue is likely that the divs from the target's default slot are re-used when the portal's content is rendered. You should put a `key` on the target's...

Yeah, I don't see a way to fix this tough

Well, the portal content is moved to the portal-target:  As I'm not familiar with that window library that you are using, someone would have to guide me about why...

Edit: this seems to be related: #287

Okay, this is getting weirder by the minute 🧐 Maybe a Chrome bug? Need to test other browsers...

Weird. Just - weird.

It seems that Vue's `h()` is aware that it's curently in an SVG element and thus creates the HTML elements differently before they are portaled to *outside* of the SVG....

I may find some time to look into it but my impression so far is that this would require a change in Vue 2 core.

I can confirm that this is indeed an issue, but so far couldn't find out what exactly is causing it or how to work around it. I likely won't have...

This is indeed a caveat, which is a consequence of the `$parent`caveat. `` internally walks the `$parent` chain to find out how many (if any) parent `` components there are....