-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid renderings #37
Comments
Strangely enough pushing the buttons enough gets it back into a good state? Perhaps it is because I am not properly mounting the socket with a default value? |
Hello<br/>
<span>Outside is: {{.Outside}}</span>
<button live-click="inside">Inside</button>
<button live-click="outside">Outside</button>
<button live-click="nothing">Nothing</button>
<details>
<summary>Advanced</summary>
<span>Inside is: {{.Inside}}</span>
<button live-click="inside">Inside</button>
<button live-click="outside">Outside</button>
<button live-click="nothing">Nothing</button>
</details>
<script src="/live.js"></script> I think if you wrap you "Outside is {{.Outside}}" and "Inside is: {{.Inside}}" in an element like a I think because your "Outside is" section was just in the body it was causing the whole body to update which was probably breaking it. |
Yes using the span fixes all the issues. I mentioned on the other issue perhaps warning if patches to entire body are happening and/or adding a small section to the readme would be helpful! |
I've seen an invalid render on firefox and had a minimal way to reproduce the issue with a minimal example. It seems like an issue with the DOM patching?
This is using v0.12.1
Click the
Inside
button first.The text was updated successfully, but these errors were encountered: