Thorsten Lünborg

I'd call this expected behaviour fom the way scoped styles and deep selectors work. This is the generated CSS: ```css [data-v-472cff63] h1 { color: red; } ``` As you can...

That still a bit fragile, however. When the target's parent gets removed from the DOM, the portal content is removed from the DOM with it - but the source component...

You will always need two different bundles as soon as components are involved, as Vue 2 and Vue 3 render functions are different. And adding that, there are other breaking...

The release was one month ago. https://github.com/vuejs/vue-router-next/releases/tag/v4.0.0 That's for Vue 3 though.

I think this is actually expected behaviour. You see, when you navigate to a route by name, vue-router will **not** render this route's default child (a child with `path: ''`)....

Hi @nicbou Thanks for the report. Could you provide an interactive reproduction via jsfiddle or a quick repository? That would help us out.

Probably also useful to determine weither to use a "forward" or "backward" transition - if the new path is the same as the referrer, user probably clicked the back button,...

Weither or not that is enough depends on the developers intend for this part of his app. And it's better than nothing, considering that there simply is no way to...

As posva said, this is expected behaviour. The docs say: > Setting [`fallback`] to false essentially makes every router-link navigation a full page refresh in IE9. History mode can't work...

Okay, then for *that* we need a demo / reproduction. Or you just send a PR. But I haven't seen this behaviour yet.