Kasper
Kasper
This bug appears in Svelte 5 too: https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE0WOzQrCMBCEX2VZPLRQ6D2mAQ8-gUfjoT9bDbRrSDaFEvruEhE8ft_AzGSc3UIR1T0j9yuhwov32KDsvkDcaBHCBuM7hbEYHcfgvBjLVhYSYOjgFKUXquqzZd3-c9beXFcvO8iLwLFPonTrjWX9BSgjnUVO60DBIgyOJ7X1S6Iu89H-OgKZcg06yDcJjp8V14dui7eMDa7vyc2OJlQSEh2P4wPqcR_a1QAAAA==
The docs were indeed updated to `null` (#9941). Is it standard behaviour that `undefined` can be bound to a value that cannot be `undefined`?
Yep, that makes sense. The input's value is `null` while the bound variable is `undefined`, aka the binding isn't working.
Could you show a UI/use case where that would be needed?
I wonder if a popover could work
Any thoughts/feedback/tips @printfn? Do you agree that this change make sense? Also, what is `Expr::Bop`?
@printfn Wanna have a look at the code? I'm not really sure how to go forward
Still reproducible
Still reproducible on 0.170.4
Sounds right, yes