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 are present before delay is reached #11682

Closed
ptrxyz opened this issue May 18, 2024 · 1 comment
Closed

Transitions are present before delay is reached #11682

ptrxyz opened this issue May 18, 2024 · 1 comment

Comments

@ptrxyz
Copy link

ptrxyz commented May 18, 2024

Describe the bug

If you set a delay for transitions, the elements are already created before the delay is reached and as soon as the delay passed, the animation starts.

The following example shows the problem:

Svelte 4:
https://svelte.dev/repl/881200de2b26406884ca2255a9f85e3f?version=4.2.17

Svelte 5:
https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA32NwUrEMBCGX2UYL4qFdg9eQltYQcGrV-OhNimEpjMlnZYNIe8u2VW8eRpm_u-bP-HkvN1QfSSkYbGo8LyuWKHEtSzbYb1YrHDjPYzl0m5jcKv0mrS4ZeUgkGDyETJMgRfQP04tYaDNiWPSWGBvBYihg0ZTW_99ofZrF2ECJjV6N85dun-Ari8wPHZwyteu17f3lyLe4KuY7mYbgTiXvDXuAEdq8rFLyexhKNUKnpqmqeCi4FSmsX6It2O-alp4l38l-AX7Z75AIs5tbdzRa0r1bGMJCStc2LjJWYNKwm7zZ_4G7eBCDFsBAAA=

Reproduction

in Svelte 4 REPL:

  • press the button. You will see that Box 0 flys out and after it's done, Box 1 appears and flys in.

in Svelte 5 REPL:

  • when you press the button, Box 1 is present while Box 0 flys out and will start flying in after the delay.

Logs

No response

System Info

System:
    OS: Linux 6.8 Arch Linux
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 48.67 GB / 62.70 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 20.13.0 - /usr/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 10.8.0 - /usr/bin/npm
    pnpm: 9.1.1 - /usr/bin/pnpm
    bun: 1.1.4 - ~/bin/bun
  Browsers:
    Brave Browser: 125.1.66.110
  npmPackages:
    svelte: 5.0.0-next.136 => 5.0.0-next.136

Severity

annoyance

@mquandalle
Copy link

Duplicate of #10876 and #11270

@dummdidumm dummdidumm closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2024
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

3 participants