Transition delay is cached and does not apply until after the next run

[GrygrFlzr]

Describe the bug
After a transition has already been triggered, changing the delay of a transition does not take effect until after the transition has been triggered at least once.

To Reproduce
REPL: https://svelte.dev/repl/48114260160b40d7bcb2f0d2dc148eb6?version=3.38.3

1. Click Menu several times to toggle the default transition.
   IMPORTANT: The bug requires triggering the transition at least once before the delay is cached.
2. Click Set Delay to 1s, the delay variable is now set to 1000.
3. Click Menu to toggle the transition, delay has not taken effect.
4. Click Menu to toggle the transition, delay now takes effect.
5. Click Set Delay to 0, the delay variable is now set to 0.
6. Click Menu to toggle the transition, 1s delay still applies.
7. Click Menu to toggle the transition, delay is now updated.

Expected behavior
I expect the delay to apply immediately, or at least applied after I do await tick().

Information about your Svelte project:
Svelte: 3.32.1, 3.38.3
Tested Browsers:

• Edge: Chromium (88.0.705.50)
• Chrome: 88.0.4324.104
• Firefox Dev: 86.0b5 (64-bit)

Severity
Low

[geoffrich]

Possibly related to #5736? In that issue, the CSS transform was cached and not updated until after the next run.

As with that issue, using in and out instead of the transition shorthand causes the delay to be updated immediately, though it is annoying to duplicate the parameters.

<nav in:fly={{
	x: -100,
	delay,
}} out:fly={{
	x: -100,
	delay,
}}>

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[geoffrich]

Still an issue.

[eytienne]

Not an issue anymore opening the link with 5.33.13