[5.43.10] Two hover preloading issues

[sillvva]

Describe the bug

In my local dev server testing, I noticed two issues in the latest Svelte version. However, I was only able to reproduce one of them in Stackblitz

• When hovering one link, then clicking another, the page does not load. This one I was able to reproduce.
• When navigating from a page with params to a page without params, the params object becomes empty when clicking the link to go to the page without params causing remote functions in the current page to error. I was not able to reproduce this in Stackblitz.

Disabling the hover preloading fixes the issues for now:

-  data-sveltekit-preload-data="hover" data-sveltekit-preload-code="eager"

Reproduction

The issue I could reproduce

https://stackblitz.com/edit/sveltejs-kit-template-default-vgnsfckn?file=package.json,src%2Froutes%2Ftest.remote.ts,src%2Froutes%2F%2Bpage.svelte,src%2Froutes%2F[test]%2F%2Bpage.svelte

The isssue I couldn't reproduce

Remote function schema validation failed: [
  {
    kind: 'schema',
    type: 'union',
    input: undefined,
    expected: '(string | "new")',
    received: 'undefined',
    message: 'Invalid type: Expected (string | "new") but received undefined',
    requirement: undefined,
    path: [ [Object] ],
    issues: [ [Object], [Object] ],
    lang: undefined,
    abortEarly: undefined,
    abortPipeEarly: undefined
  }
]

Logs

System Info

System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 235.27 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/node
    npm: 11.6.1 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/npm
    pnpm: 10.21.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/pnpm
    bun: 1.2.20 - /Users/sillvva/.bun/bin/bun
  Browsers:
    Firefox: 144.0
    Safari: 26.1
  npmPackages:
    svelte: 5.43.10 => 5.43.10

Severity

blocking an upgrade

[nathancahill]

Ran in to this as well. Calling remote functions with client side navigation (preload or just simple navigation) has getRequestEvent returning the event of the current page rather than the target page. A very simple repro is two routes with a link between them. Loading from the server resolves the event correctly, loading from the client resolves to the previous event.

[paoloricciuti]

This should be fixed by #17163