Repository navigation
<select> displays wrong choice when options are dynamically updated #17148
Description
Describe the bug
If a <select> is bound to a state not equal to the initial value and its options are updated, the element will snap to display the initial value that does not match the state variable. This issue was introduced in 5.41.0, it does not occur in 5.40.2.
Reproduction
- Add option
- Select option that is not the initial value
- Add another option
<select>now displays the wrong option
With an $effect snapping to a different (still wrong) value
svelte.dev
- Add 2 options
- Select option that is not 0
- Add another option
<select>now displays the wrong option
Logs
System Info
Chromium 140.0.7339.185
Firefox 145.0
Safari 26.1 (21622.2.11.11.9)Severity
blocking an upgrade
Reacted by brunnerh, CHFR, MMaker, sukeshpabolu, Vlad Shcherbin, baileyherbert, Mikołaj Dunikowski and Falco
Activity
falco467 commentedon Feb 9, 2026
This is a severe regression bug introduced with version 5.41 which is producing a lot of irritation and problems without a clear workaround to mitigate. It is currently a blocking problem for us as well.
falco467 commentedon Feb 9, 2026
I think the problem was probably introduced by this commit:
#16958
from @Rich-Harris
If the Options-List is updated while the select is the active Element the update is skipped. But if the option list changes the update is neccessary, even if the select has focus, since it needs to update to display the value correctly.
fix: keep select.__value current when effect is deferred (sveltejs#17148
fix: keep select.__value current when effect is deferred (#17745)