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
This is a weird one that I'm able to consistently reproduce (see repro below) on latest version of Svelte 5, Superforms, Formsnap, and Bits UI. Whenever a form input binds to control attrs, which is the recommended approach, any event handlers attached to that input do not fire. However, removing the {...attrs} spread appears to work:
This is more of a formsnap issue than a bits-ui issue. I would transfer this over to the formsnap repo, though it doesn't look like I'm able to at the moment.
This one has me bit baffled. Here are some weird quirks I've observed so far:
Commenting out/removing the <Form.FieldErrors /> component restores the behavior
Changing attrs to a normal variable (let attrs = ...) instead of a reactive declaration ($: attr = ...) also "fixes" it, however it's not a true fix as it won't react to changes to its dependencies
With that said, I'm thinking this is may be a weird Svelte 5 issue. Can you post this issue to the Svelte 5 libraries thread?
Describe the bug
This is a weird one that I'm able to consistently reproduce (see repro below) on latest version of Svelte 5, Superforms, Formsnap, and Bits UI. Whenever a form input binds to control attrs, which is the recommended approach, any event handlers attached to that input do not fire. However, removing the
{...attrs}
spread appears to work:Broken:
Working:
Reproduction
Logs
No response
System Info
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: