-
Notifications
You must be signed in to change notification settings - Fork 120
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
xilem_web: Possible bug when using .boxed
and changing type of HTML node
#465
Comments
Philipp-M
added a commit
to Philipp-M/xilem
that referenced
this issue
Jul 29, 2024
…ld element in the DOM-tree
Philipp-M
added a commit
to Philipp-M/xilem
that referenced
this issue
Jul 29, 2024
…in the DOM-tree
Thanks for the repro, that made fixing this easy, internally the element was changed, but the actual DOM node in the tree wasn't. |
Nice! Thanks for the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think I found an issue when using
.boxed
combinator from #460 and using it to dynamically change the type of HTML element.I created a minimal reproduction here, which looks like this:
The boxed element keeps it's initial type and text, even when the button is clicked. If the state is
false
initially, it stays a<span>
, and iftrue
a<div>
.The text was updated successfully, but these errors were encountered: