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
I have doubts about whether the states are transferred correctly when using a library that I have in Svelte 4 in Svelte 5. While it works without any problems in Svelte 4, it does not work the same way in Svelte 5.
I prepared an app that changes the radio value every second. If you look at the links in reproduction, you can understand the problem exactly.
Avoid going through the `element.value = element.__value = newValue` condition because `__value` is actually how Lit stores the current value on the element, and messing with that would break things: Lit would think the value hasn't changed (because `__value` is already set to the new value by us) and doesn't fire an update.
fixes#15194
Avoid going through the `element.value = element.__value = newValue` condition because `__value` is actually how Lit stores the current value on the element, and messing with that would break things: Lit would think the value hasn't changed (because `__value` is already set to the new value by us) and doesn't fire an update.
fixes#15194
Describe the bug
I have doubts about whether the states are transferred correctly when using a library that I have in Svelte 4 in Svelte 5. While it works without any problems in Svelte 4, it does not work the same way in Svelte 5.
I prepared an app that changes the radio value every second. If you look at the links in reproduction, you can understand the problem exactly.
Reproduction
Svelte 4: https://stackblitz.com/edit/vitejs-vite-bqjij8vn?file=src%2FApp.svelte
Svelte 5: https://svelte.dev/playground/00f889e5d7f84dbbaba90c6014fb5606?version=5.19.6
Logs
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: