Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Submitted forms don't carry the "submitter" attribute

未关闭
  • 哪里不对？
#709 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
elixir
领域
backend

调研方向

Reproduce the issue with Surface Form components and two named submit buttons using the provided example, then trace the form submission handling. Done means the params map includes submit=save or submit=submit according to the button clicked, matching native Phoenix LiveView behavior.

由索引模型根据 Issue 内容生成。

描述

Describe the bug

Phoenix gained the ability to distinguish between which submit button was clicked in https://github.com/phoenixframework/phoenix_live_view/pull/2490. Unfortunately, this doesn't work with the default way surface handles form submit.

How to reproduce it

  1. Create a form using <Form> components, with 2 submit buttons. Ensure the submit buttons have a name and value attribute set 
    <Form
  for={@changeset}
  trigger_action={false}
  submit="submit"
  change="change"
>
  <button type="submit" name="submit" value="submit">Submit</button>
  <button type="submit" name="submit" value="save">save</button>
</Form>
  2. Attempt to submit the form using either button. You will not see the submit as a value in the params map

The behavior you expected

I should see the submit value as either save or submit, depending on the button that was clicked. This is how it works in native Phoenix LiveView

Your Environment

Surface: v0.11.0
LiveView: v0.19.5
Elixir: 1.14.4-otp-25

主要语言
Elixir
星标
2.1k
派生
146
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

surface-ui/surface 的其他 Issue

查看 surface-ui/surface 的全部 Issue

相似的 Issue

更多 Elixir Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。