fix: better input cursor restoration for bind:value

[dummdidumm]

If cursor was at end and new input is longer, move cursor to new end

No test because not possible to reproduce using our test setup.

Follow-up to #14649, fixes #16577, fixes #14979

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.
• If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

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

[changeset-bot]

🦋 Changeset detected

Latest commit: c3e91a3

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

[svelte-docs-bot]

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

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@16925

[theodorejb]

It looks like this will resolve #16577. With this change my original oninput and bind:value approach now works as expected in all browsers:

https://svelte.dev/playground/bf28bf223e4746a199f15ca80385487d?version=pr-16925

I believe this will also resolve #14979.

[dummdidumm]

Huh, never would've thought this fixes the Firefox bug, that seemed different to selection problems. But even better 😄