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

Local transition in #each block is is disabled if parent node has out transition cancelled #5829

Closed
arackaf opened this issue Dec 27, 2020 · 1 comment · Fixed by #5841
Closed

Comments

@arackaf
Copy link
Contributor

arackaf commented Dec 27, 2020

Is this about svelte@next? This project is currently in a pre-release stage and breaking changes may occur at any time. Please do not post any kind of bug reports or questions on GitHub about it.

No

Describe the bug
A clear and concise description of what the bug is.

Items inside of an #each block have a local out transition. The parent node has a transition defined on it. If said parent node is unmounted, but then re-mounted before its transition finishes, the transitions in the items in the each block no longer work.

REPL: https://svelte.dev/repl/388e9996f8464f88b9e65a569c34912d?version=3.31.0

Logs
Please include browser console and server logs around the time this bug occurred.

N/A

To Reproduce
To help us help you, if you've found a bug please consider the following:

I gotchu boo: https://svelte.dev/repl/388e9996f8464f88b9e65a569c34912d?version=3.31.0

  • If that's not possible, we recommend creating a small repo that illustrates the problem.
  • Reproductions should be small, self-contained, correct examples – http://sscce.org.

Occasionally, this won't be possible, and that's fine – we still appreciate you raising the issue. But please understand that Svelte is run by unpaid volunteers in their free time, and issues that follow these instructions will get fixed faster.

Expected behavior
A clear and concise description of what you expected to happen.

out transition should work

Stacktraces
If you have a stack trace to include, we recommend putting inside a <details> block for the sake of the thread's readability:

N/A

Stack trace

Stack trace goes here...

Information about your Svelte project:
To make your life easier, just run npx envinfo --system --npmPackages svelte,rollup,webpack --binaries --browsers and paste the output here.

N/A

  • Your browser and the version: (e.x. Chrome 52.1, Firefox 48.0, IE 10)

Chrome 87

  • Your operating system: (e.x. OS X 10, Ubuntu Linux 19.10, Windows XP, etc)

Mac

  • Svelte version (Please check you can reproduce the issue with the latest release!)

Whatever's in the REPL

  • Whether your project uses Webpack or Rollup

N/A

Severity
How severe an issue is this bug to you? Is this annoying, blocking some users, blocking an upgrade or blocking your usage of Svelte entirely?

High

Note: the more honest and specific you are here the more we will take you seriously.

Additional context
Add any other context about the problem here.

@Conduitry
Copy link
Member

This is fixed in 3.31.1 - https://svelte.dev/repl/388e9996f8464f88b9e65a569c34912d?version=3.31.1

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

Successfully merging a pull request may close this issue.

2 participants