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
{{ message }}
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.
My use case for snabbdom-virtualize is to “pick up where I left off” with a server-rendered DOM: snabbdom’s patch(oldVnode, newVnode) function expects both oldVnode and newVnode to be virtual, so I was hoping to virtualize the existing DOM before patch()ing with the next state.
However, snabbdom needs the .elm reference to tie elements up properly, which snabbdom-virtualize doesn’t set.
Is there any reason why setting .elm to refer to the source node would be a bad idea?
The text was updated successfully, but these errors were encountered:
I wonder if
virtualize()
should set the.elm
property on the nodes it creates, such that:Reasoning:
My use case for
snabbdom-virtualize
is to “pick up where I left off” with a server-rendered DOM: snabbdom’spatch(oldVnode, newVnode)
function expects botholdVnode
andnewVnode
to be virtual, so I was hoping to virtualize the existing DOM beforepatch()
ing with the next state.However, snabbdom needs the
.elm
reference to tie elements up properly, whichsnabbdom-virtualize
doesn’t set.Is there any reason why setting
.elm
to refer to the source node would be a bad idea?The text was updated successfully, but these errors were encountered: