nextjs - 💡(How to fix) Fix `next/form` does not send values on buttons with `type="submit"` [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#84857Fetched 2026-04-08 02:18:09
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
1
Author
Participants
Timeline (top)
commented ×2issue_type_added ×1labeled ×1

Code Example

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 16.0.0-canary.4 // Latest available version is detected (16.0.0-canary.4).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/agitated-hodgkin-zndkl2

To Reproduce

  1. Start the next app and navigate to /
  2. Click on Submit in the next/form Form
  3. Click on Submit in the vanilla HTML Form

Current vs. Expected behavior

Currently, the behavior between both differs. With next/form the value specified on the <button type="submit"> does not get sent to the backend, while it does get sent with the normal form.

I would expect the two implementations to behave identically, apart from next/form doing client side navigation.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 16.0.0-canary.4 // Latest available version is detected (16.0.0-canary.4).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Form (next/form)

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

Additional context

No response

extent analysis

TL;DR

The issue can likely be resolved by adjusting the next/form configuration to include the submit button value in the form data.

Guidance

  • Review the next/form documentation to ensure that the submit button value is being properly handled and included in the form data.
  • Verify that the name attribute is set on the submit button element, as this is typically required for the value to be included in the form submission.
  • Compare the implementation of the next/form form with the vanilla HTML form to identify any differences in how the submit button value is being handled.
  • Check the Next.js version and consider upgrading to a newer version if available, as the issue may have been resolved in a later release.

Example

No code example is provided, as the issue is more related to configuration and implementation details.

Notes

The issue seems to be specific to the next/form package and its interaction with Next.js. The provided environment information and package versions may be relevant in troubleshooting the issue.

Recommendation

Apply workaround: Adjust the next/form configuration to properly handle the submit button value, as this is likely the cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix `next/form` does not send values on buttons with `type="submit"` [2 comments, 2 participants]