cached linker in v-if may lead to wrong host and unexpected behaviours #1185
Description
Test Version: v0.12.10
In v-if, it will cache the linker if the constructor and the element's html are the same. However, the linker is relative to the host. It means it will lead to some hard-to-discover unexpected behaviours. For example as followed, the comp-b in #two won't fire any ready / attached events! Because
- After the
#oneattached, the program will compile and link the#two. - When binding the
v-ifdirective forcomp-bin#two's template, the directive will fetch the linker from the cache (whose host is thecomp-ain#one!). - The directive invoke the
updateand compile and link thecomp-b. - The
comp-bwill be added into#one'scomp-a's$childrenlist. - Then it will check if need to fire the
attachedevent, however, because the host (thecomp-bin#one) is attached, it won't fire it!
<template id="comp-c">
<comp-a>
<comp-b v-if="some-condition-true">Something</comp-b>
</comp-a>
</template>
<template id="comp-a">
<content></content>
</template>
<template id="comp-b">
<content></content>
</template>
<body>
<div id="app">
<comp-c id="one"></comp-c>
<comp-c id="two"></comp-c>
</div>
</body>