Remote functions: radios / `fields.value()` out of sync after same-URL `form()` success

[janekprange]

Describe the bug

Same-URL remote form() edit page, backed by a query(). After a successful Save the query already has the new values, but radios / select / checkbox selection and fields.value() don't stay in sync. Calling query().refresh() in the handler doesn't help.

Default {...form} enhance runs element.reset() after success (client form). On the server, success stores a submission without input, and fields.set(...) returns early (don't override a submission) (server form).

How that lands per control:

• .as('text', queryValue) from feat: allow second value for all types of fields #15577 can still look fine (get_value() ?? secondArg).
• .as('radio', option) can't. The second arg is the option identity, not "current selection", so once input is emptied nothing stays checked.
• checkbox has no second arg at all.
• select is passed the current value (.as('select', queryValue), same as text) but still breaks with JS: after reset() + the submission lock it falls back to the first option.

Text is the only control that comes back correctly.

redirect(303) only works around this when it actually navigates. Without JS the browser does a real 303 then GET; fresh page, fields match. With JS, a redirect to the same URL is handled as a client invalidateAll (no navigation, no remount), so you get the same stay-on-page bug. It only helps when the target URL is different.

Docs point edits at stay-on-page + .as(type, value), and mostly show redirect for create → new URL. Always-redirect doesn't look like the prescribed path. Reset-on-success (#14322) and ignoring set after submission (#15465) do look intentional.

It would be nice if this could "just work" like the text input already does.

Reproduction

https://stackblitz.com/github/janekprange/sveltekit-remote-form-post-success-rehydrate

Repo: https://github.com/janekprange/sveltekit-remote-form-post-success-rehydrate

The no-js routes throw a 500 on StackBlitz/WebContainer. They work on a real Node runtime; run the repo locally for those. This is reported in issue #16818.

1. Open /default (default enhance, JS on). Change visibility / frequency / marketing / title, Save.
2. Query dump shows the new values, but the controls revert to their defaults (radios → default option, select → first option) and fields.value() is stale. Only the title text input stays correct. A plain reload fixes it (clean GET).
3. Open /default/no-js via the no-JS page link (data-sveltekit-reload + csr = false). Same broken end-state after Save: you land on the ?/remote=… action URL. A plain reload re-runs the submission and stays broken. Navigate away and back (clean GET) to fix it.
4. /custom-enhance: with JS, skipping reset() keeps both the DOM selection and fields.value() correct across repeated saves (workaround). /custom-enhance/no-js stays broken since there is no enhance without JS.
5. /redirect: with JS this is broken like /default, because returnTo is the same URL and the client handles the redirect as invalidateAll (no navigation or remount). /redirect/no-js works: a real 303 then GET lands on a fresh page whose fields match the query.

Logs

System Info

Binaries:
  Node: 25.2.1
  pnpm: 10.31.0
npmPackages:
  @sveltejs/adapter-auto: next => 8.0.0-next.3
  @sveltejs/kit: next => 3.0.0-next.23
  @sveltejs/vite-plugin-svelte: ^7.2.0 => 7.3.0
  svelte: ^5.56.7 => 5.56.9
  vite: ^8.1.5 => 8.2.1

Severity

annoyance

Additional Information

App-side workaround I use today: custom .enhance() without reset() for JS, plus redirect(303) when !getRequestEvent().isRemoteRequest for no-JS.

Related:

• Remote functions: Impossible to set form values post-submission when CSR disabled #15465 / feat: allow second value for all types of fields #15577 — set after submission ignored on purpose; .as second arg helps text-like fields
• fix: reset form inputs by default when using remote form functions #14322 — default reset() after enhanced success is intentional
• Remote Functions: form update clears inputs on second submit #14729 — stay-on-page update forms clearing inputs
• feat: allow setting dynamic values in remote forms #16160 — dynamic initial values for edit forms
• Remote form flashes blank inputs before redirect completes #16689 / Way to know whether remote function is redirecting us #15725 — redirect is a common success path; reset vs _goto timing