Patrick

Just to make sure no one that comes across this thread uses this to secure their `load` functions: > You need to ensure that your layout reruns on every page...

Moving from `` to `` might be confusing.

Sounds good. And how would the SSR output look like? I guess it would be handled like a normal html element, so there would be a `src` attribute, right?

There is also a proposal for component scoped transitions which should be the default IMO: https://github.com/sveltejs/svelte/issues/8850

[Minimal reproduction](https://www.sveltelab.dev/3zywbxz24nh8ege)

The maintainers probably haven't discussed this yet, but I think this should be optional as Rich [mentioned](https://github.com/sveltejs/kit/issues/11956#issuecomment-2083469945) in the issue. Also, I don't think this is the correct fix. This...

The reason I mentioned SSR is because the solution for the linked issue #11956 (which is about `$page.state` not `history.state`) should work with SSR enabled as well. I guess this...

~~Wouldn't it be enough to change line 1531?~~ ```diff -_preload_code(/** @type {HTMLAnchorElement} */ (entry.target).href); +_preload_code(/** @type {HTMLAnchorElement} */ (entry.target).pathname); ``` nvm. It wouldn't run the `reroute` hook. BTW: `_preload_code()` in...

@orisrightpaw Can you explain why the `readableAborted` check is needed? Wouldn't this work? ```diff request.once('close', () => { - if (request.readableAborted) { controller.abort(); - } }); ``` If it is...

~~In your repo (I guess you mean the code in `src/routes/+page.svelte`), the warnings are correct. You don't have elements with a `my-container` or `my-list` id.~~ Missed the `( expected css(css-lparentexpected)`...