Skip to content
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

Transitions in await create duplicate DOM nodes #3431

Closed
skhavari opened this issue Aug 20, 2019 · 6 comments
Closed

Transitions in await create duplicate DOM nodes #3431

skhavari opened this issue Aug 20, 2019 · 6 comments

Comments

@skhavari
Copy link

skhavari commented Aug 20, 2019

Describe the bug
transitions in await blocks cause duplicate DOM nodes

To Reproduce
Click update a couple times in this REPL

Expected behavior
No duplicate nodes in the DOM

@dasZGFz
Copy link
Contributor

dasZGFz commented Aug 20, 2019

I'm having the same issue. Here's a slightly smaller reproduction of the issue: REPL

@skhavari skhavari changed the title Transitions in await create duplicate nodes Transitions in await create duplicate DOM nodes Aug 20, 2019
@dasZGFz
Copy link
Contributor

dasZGFz commented Aug 22, 2019

I updated the REPL after a discovery: the bug only appears with transition out and not with transition in.

@cdock1029
Copy link

previous issue:

#1591

@mylastore
Copy link

Why is this issue closed I am have the same issue with transitions not removing the previous DOM nodes?

@whishkid
Copy link

whishkid commented Jun 4, 2020

I also have this issue,
if you are replacing an object (causing transition out, and transition in) it seems to help to delay adding the next object until the transition out has finished (setTimeout)

@Conduitry
Copy link
Member

This is closed because it's a duplicate of #1591.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants