-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[svelte 5]: value
should be assigned and cleared here
#11363
Comments
Just chipping in... I agree it seems to be a regression. It seems to be related to the same prop being assigned the same value from two different components. Here is a smaller example with runes. Putting the last example into Svelte 4 works fine. |
using |
Yeah. But this is a workaround. |
I believe the minimum reproduction is this. It seems that a derived value getting read, then another dependency triggering a rerun which results in the same value, and then a render effect reading the derived falsely makes that render effect believe nothing has changed. The other reproductions use props in a way that trigger the hardest variant of the internal |
previously a reaction could be marked as DIRTY and subsequently as MAYBE_DIRTY before running, resulting in false negatives. Ensure that DIRTY flag can never be lowered to MAYBE_DIRTY fixes #11363
Describe the bug
I'm trying Svelte 5 for the first time today.
This is a reproduction of this issue.
PLEASE USE CHROME since Firefox does not emit
onchange
event.As you can see if I select a date from the picker the
{value}
is not assigned and the same if I press the "Clear" button.Why?
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: