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
The rest of the file is the same as in the Brr example. If I replace the last line with button, the button no longer updates.
I'm guessing this is due to the mismatch between the pure interface and the statefulness of the DOM. Should we always ensure that the top-level node is not dynamic, or is there a better workaround? Maybe this could be documented somewhere.
Indeed, there is a mismatch, usually just at the node at the junction between Lwd and DOM.
The commented line is meant to address that though this solution has shortcomings too.
First it would be nice to check that the ui node is not already the only child of body. Otherwise the side effect might reset some internal browser state (such as focused element and selected text).
And then, it works if there is only a single child, since it removes all other nodes. That could be worked around, but I have no time to spend on that in the near future :/.
Hi, I was trying out the Brr backend and had a couple of questions.
The rest of the file is the same as in the Brr example. If I replace the last line with
button
, the button no longer updates.Anyway, I really like Lwd so far, awesome work!
The text was updated successfully, but these errors were encountered: