-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
select
with reactive disabled
attribute hides the binded value
#16030
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
Comments
Hi. |
Mmm it's weird that my PR broke this as this is a reactivity issue and I only touched the server code |
Oh yeah I suppose the culprit was actually #15961 |
When you render the pages with let userData = $state( ... and at some point you update the values, but the change is not reflected, instead it gets to empty no selected value. This works this do not work
Thanks |
This two snippets are the same 😄 Btw i think i found the bug |
Are not the same: Looks like working in 5.33.8. Thanks |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Might relate to: #16017.
After upgrading to
5.33.5
select
withdisabled
state behaves unexpectedly.When setting
disabled
attribute toselect
component (just a wrapper aroundselect
element), then the bindedvalue
suddenly disappears.While reproducing the issue I figured out few things:
select
has to be in separated file as component to reproduce itbind:value
and change it tovalue={value}
inside select component, it worksdisabled
prop from select component, it worksReproduction
Broken >= 5.33.5
https://svelte.dev/playground/6d9f0dbfa2c74e8f88483dd90d0abfd6?version=5.33.7
Working < 5.33.5
https://svelte.dev/playground/6d9f0dbfa2c74e8f88483dd90d0abfd6?version=5.33.4
System Info
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: