You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 #one attached, the program will compile and link the #two.
When binding the v-if directive for comp-b in #two's template, the directive will fetch the linker from the cache (whose host is the comp-a in #one!).
The directive invoke the update and compile and link the comp-b.
The comp-b will be added into #one's comp-a's $children list.
Then it will check if need to fire the attached event, however, because the host (the comp-b in #one) is attached, it won't fire it!
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, thecomp-b
in#two
won't fire anyready
/attached
events! Because#one
attached, the program will compile and link the#two
.v-if
directive forcomp-b
in#two
's template, the directive will fetch the linker from the cache (whose host is thecomp-a
in#one
!).update
and compile and link thecomp-b
.comp-b
will be added into#one
'scomp-a
's$children
list.attached
event, however, because the host (thecomp-b
in#one
) is attached, it won't fire it!The text was updated successfully, but these errors were encountered: