fix: preload data on tap after code was preloaded on hover

[teemingc]

fixes #13466 (for real this time)

#13486 previously fixed the preload on tap not working by ensuring we do not skip checking the link until a preload has triggered. However, there's also the case where we have both preload link options: preload code on hover and preload data on tap.

This PR ensures that we still preload data on tap even after a successful preload on hover if the preload on hover was only preloading code.

---

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0633140

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@sveltejs/kit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-13530-svelte.vercel.app/

[elliott-with-the-longest-name-on-github]

Are you sure? I could've hovered like 10 minutes ago if I left for another tab, or to eat a sandwich or something, then came back and hovered again -- not sure we'd want to serve stale data in that case

[teemingc]

I think this has already been the behaviour since we cache the load data on hover. Additionally, @dummdidumm added the a === current_a skip condition as part of the server-side route resolution PR and it does help to skip more of the preload code while hovering over the same link (previously, you could move your mouse across the same link and this function would get called every 20ms).

Maybe we should add a timer to expire the load data cache?

[dummdidumm]

We can investigate that separately - for now this looks good to fix the bug