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
No REPL demo until #525 is released, but if you have a situation like this...
{{#each things as thing @name}}
<divout:fade>{{thing.name}}</div>
{{/each}}
...then when you remove an item from the middle of things, the corresponding DOM node jumps to the top of the list. That's because Svelte mounts all iterations that correspond to the current value of things, in order, to whatever the anchor node is — it doesn't mount outroing nodes, with the effect being that everything preserved or created appears below everything outroing.
There isn't really a neat solution to this — instead we'll need to implement #373.
The text was updated successfully, but these errors were encountered:
This is mostly fixed in 1.20 — REPL. However it seems that if you bash the 'randomise' button in the example enough times, you can get into a corrupted state (one of the letters on the left hand side will stick around when it should have been removed). Haven't yet managed to create a minimal repro that we can work with — if anyone is able to, that would be a huge help!
No REPL demo until #525 is released, but if you have a situation like this...
...then when you remove an item from the middle of
things
, the corresponding DOM node jumps to the top of the list. That's because Svelte mounts all iterations that correspond to the current value ofthings
, in order, to whatever the anchor node is — it doesn't mount outroing nodes, with the effect being that everything preserved or created appears below everything outroing.There isn't really a neat solution to this — instead we'll need to implement #373.
The text was updated successfully, but these errors were encountered: