我认为这篇文章会帮助如果有人想用jQuery:

http://greatwebguy.com/programming/dom/default-html-button-submit-on-enter-with-jquery/

基本解决方案是:

$(function() {
    $("form input").keypress(function (e) {
    if ((e.which && e.which == 13) || (e.keyCode && e.keyCode == 13)) {
        $('input[type=submit].default').click();
        return false;
    }
    else {
        return true;
    }
    });
});

另一个我喜欢的是:

jQuery(document).ready(function() {
    $("form input, form select").live('keypress', function (e) {
        if ($(this).parents('form').find('button[type=submit].default, input[type=submit].default').length <= 0)
            return true;

        if ((e.which && e.which == 13) || (e.keyCode && e.keyCode == 13)) {
            $(this).parents('form').find('button[type=submit].default, input[type=submit].default').click();
            return false;
        }
        else {
            return true;
        }
    });
});

Andrezj的答案几乎是完美的……但这里有一个简单的跨浏览器解决方案。

取这样的形式:

<form>
    <input/>
    <button type="submit" value="some non-default action"/>
    <button type="submit" value="another non-default action"/>
    <button type="submit" value="yet another non-default action"/>

    <button type="submit" value="default action"/>
</form>

然后重构为:

<form>
    <input/>

    <button style="overflow: visible !important; height: 0 !important; width: 0 !important; margin: 0 !important; border: 0 !important; padding: 0 !important; display: block !important;" type="submit" value="default action"/>

    <button type="submit" value="some non-default action"/>
    <button type="submit" value="another non-default action"/>
    <button type="submit" value="yet another non-default action"/>
    <button type="submit" value="still another non-default action"/>

    <button type="submit" value="default action"/>
</form>

由于W3C规范指出多个提交按钮是有效的，但忽略了关于用户代理应该如何处理它们的指导，所以浏览器制造商只能按照他们认为合适的方式来实现。我发现他们要么提交表单中的第一个提交按钮，要么在当前有焦点的表单字段之后提交下一个提交按钮。

不幸的是，简单地添加一个显示样式:none;这是行不通的，因为W3C规范指出任何隐藏元素都应该从用户交互中排除。所以把它藏在众目睽睽之下吧!

上面是我最终投入生产的解决方案示例。按enter键触发默认表单提交，即使在DOM中出现其他非默认值并在默认提交按钮之前也是如此。与显式用户输入的鼠标/键盘交互的额外好处，同时避免JavaScript处理程序。

Note: tabbing through the form will not display focus for any visual element yet will still cause the invisible button to be selected. To avoid this issue, simply set tabindex attributes accordingly and omit a tabindex attribute on the invisible submit button. While it may seem out of place to promote these styles to !important, they should prevent any framework or existing button styles from interfering with this fix. Also, those inline styles are definitely poor form, but we're proving concepts here... not writing production code.

要确定按enter键时按下了哪个按钮，可以用type="submit"标记它，其他按钮用type="button"标记它们。例如:

<input type="button" value="Cancel" />
<input type="submit" value="Submit" />

抱歉，当我写这个答案时，我想的是一般意义上的提交按钮。下面的答案不是关于多个type="submit"按钮，因为它只留下一个type="submit"，而把另一个改为type="button"。我把答案留在这里作为参考，以防帮助可以更改表单类型的人。

我纠结于同样的问题，因为我在表单中间有一个提交按钮，可以重定向提交到另一个页面，就像这样:

<button type="submit" onclick="this.form.action = '#another_page'">More</button>

当用户按下Enter键时，单击的是这个按钮，而不是另一个提交按钮。

所以我做了一些基本的测试，创建了一个带有多个提交按钮和不同可见性选项的表单，并创建了一个onclick事件来提醒哪个按钮被单击:https://jsfiddle.net/aqfy51om/1/

我用于测试的浏览器和操作系统:

窗户

谷歌Chrome 43(来谷歌搜索:D) Mozilla Firefox 38 Internet Explorer 11 Opera 30.0

OS X

谷歌Chrome 43 Safari 7.1.6

尽管应用了可见性选项，但大多数浏览器都点击了第一个按钮，除了ie和Safari会单击第三个按钮，这是一个“隐藏”容器中的“可见”按钮:

<div style="width: 0; height: 0; overflow: hidden;">
    <button type="submit" class="btn btn-default" onclick="alert('Hidden submit button #3 was clicked');">Hidden submit button #3</button>
</div>

所以我的建议，也就是我自己的建议是:

如果你的表单有多个不同含义的提交按钮，那么在表单的开头包含一个默认动作的提交按钮，它可以是:

完全可见 用style="width: 0;高度:0;溢出:隐藏。”

另一种选择可能是偏移按钮(仍然在from的开头)style="position: absolute;左:-9999 px;顶部:-9999px;"，刚刚尝试在Internet Explorer -工作，但我不知道它还能搞砸什么，例如打印..

HTML 4并没有将其显式化。HTML 5规定第一个提交按钮必须是默认的:

4.10.21.2隐式提交 表单元素的默认按钮是按树顺序排列的第一个提交按钮，其表单所有者就是该表单元素。 如果用户代理支持让用户隐式提交表单 (例如，在某些平台上，在输入文本时按下“enter”键 控件隐式地提交表单)，然后为 表单，其默认按钮具有激活行为，但没有 禁用时，必须导致用户代理在此触发单击事件 默认按钮。

如果你想在保持视觉顺序的同时影响哪个是“第一个”，那么你可以采取一些方法。

一个屏幕外、无法对焦的按钮。

.hidden-default { 位置:绝对的; 左:-9999 px; ｝ < >形式 <输入名称= " text " > <button name="submit" value="wanted" class="hidden-default" tabindex="-1"></button> <button name="submit" value="not wanted">不是默认值 <button name="submit" value="wanted">看起来像默认的</button> > < /形式

Flexbox顺序:

.ordering { 显示:inline-flex; ｝ . ordered按钮{ 秩序:2; ｝ .订购按钮+按钮{ 顺序:1; ｝ < >形式 <输入名称= " text " > < div class = "排序" > <button name="submit" value="wanted">文件顺序第一个</button> <button name="submit" value="not wanted">在文档顺序中的第2位</button> . </button> . <button name="submit" value="not wanted < / div > > < /形式

If you submit the form via JavaScript (i.e., formElement.submit() or anything equivalent), then none of the submit buttons are considered successful and none of their values are included in the submitted data. (Note that if you submit the form by using submitElement.click() then the submit that you had a reference to is considered active; this doesn't really fall under the remit of your question since here the submit button is unambiguous but I thought I'd include it for people who read the first part and wonder how to make a submit button successful via JavaScript form submission. Of course, the form's onsubmit handlers will still fire this way whereas they wouldn't via form.submit() so that's another kettle of fish...)

If the form is submitted by hitting Enter while in a non-textarea field, then it's actually down to the user agent to decide what it wants here. The specifications don't say anything about submitting a form using the Enter key while in a text entry field (if you tab to a button and activate it using space or whatever, then there's no problem as that specific submit button is unambiguously used). All it says is that a form must be submitted when a submit button is activated. It's not even a requirement that hitting Enter in e.g. a text input will submit the form.

我相信Internet Explorer会选择在源代码中首先出现的提交按钮;我有一种感觉，Firefox和Opera会选择标签索引最低的按钮，如果没有其他定义，就会退回到第一个定义的按钮。关于提交是否具有非默认值属性IIRC，也存在一些复杂性。

The point to take away is that there is no defined standard for what happens here and it's entirely at the whim of the browser - so as far as possible in whatever you're doing, try to avoid relying on any particular behaviour. If you really must know, you can probably find out the behaviour of the various browser versions, but when I investigated this a while back there were some quite convoluted conditions (which of course are subject to change with new browser versions) and I'd advise you to avoid it if possible!