fix: trigger again when window listener already handled

[xxkl1]

fixes #10271

the window case was not handle when query listener had handled.

why test ok in before pr #10307?

because window in event.composedPath() at jsdom is

// run in jsdom
const l = event.composedPath()
// log window in l is
Object [Window] {
  ...
}

but other case is

// run in jsdom
console.log(window)
// ->
Object [global] {
 ...
}

so event.composedPath().indexOf(window) is away equal -1.
the following code will skips the event handle and makes the test pass.

svelte/packages/svelte/src/internal/client/render.js

Lines 1430 to 1435 in 506196b

	const handler_idx = path.indexOf(handler_element);
	if (handler_idx === -1) {
	// handle_idx can theoretically be -1 (happened in some JSDOM testing scenarios with an event listener on the window object)
	// so guard against that, too, and assume that everything was handled at this point.
	return;
	}

it seems to be jsdom's bug, there is no way to test this case in jsdom.

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
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests and linting

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

[changeset-bot]

🦋 Changeset detected

Latest commit: 7039ae1

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

This PR includes changesets to release 1 package

Name	Type
svelte	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

[trueadm]

It just occurred to me that we should probably be using the ownerDocument from the target element because of iframes rather than the global document object.

[dummdidumm]

On first look I thought "yeah makes sense", but on second look: The fallback event listener is set to document, too - should that one be using container_target.ownerDocument, too? Either way, this sounds like something we can talk about separately.

[dummdidumm]

Thank you!