答:更新

KeyDown

当你按住键时，会触发多次。 触发元键。

键盘按键

当你按住键时，会触发多次。 不触发元键。

KeyUp

当你释放钥匙时，最后会触发一次。 触发元键。

这是addEventListener和jQuery中的行为。

https://jsbin.com/vebaholamu/1/edit?js,console,output <——试试例子

(答案已编辑正确的回答，截图和示例)

当键按下时，Onkeydown被触发(就像在快捷键;例如，在Ctrl+A中，按下Ctrl键。

Onkeyup在按键释放时被触发(包括modifier/etc按键)

Onkeypress被触发为onkeydown和onkeyup的组合，或者取决于键盘重复(当onkeyup没有被触发时)。(我还没有测试过这种重复行为。如果要测试，请添加注释!)

textInput(仅webkit)在输入一些文本时被触发(例如，Shift+A将输入大写的“A”，但Ctrl+A将选择文本而不输入任何文本输入。在这种情况下，所有其他事件被触发)

只是想分享一个好奇心:

当使用onkeydown事件来激活一个JS方法时，该事件的charcode与你使用onkeypress得到的不一样!

例如，当使用onkeypress时，numpad键将返回与字母键上方的数字键相同的字符代码，但当使用onkeydown时则不是!

我花了相当多的时间来弄清楚为什么我的脚本在使用onkeydown时检查某些字符码失败!

演示:https://www.w3schools.com/code/tryit.asp?filename=FMMBXKZLP1MK

是的。我知道方法的定义是不同的。但非常令人困惑的是，在这两个方法中，事件的结果是使用event. keycode ..但是它们不会返回相同的值。不是一个非常声明性的实现。

似乎onkeypress和onkeydown做的是一样的(在上面已经提到的快捷键的小差异中)。

你可以试试这个:

<textarea type="text" onkeypress="this.value=this.value + 'onkeypress '"></textarea>
<textarea type="text" onkeydown="this.value=this.value + 'onkeydown '" ></textarea>
<textarea type="text" onkeyup="this.value=this.value + 'onkeyup '" ></textarea>

你会看到onkeypress和onkeydown事件都是在按下键时触发的，而不是在按下键时触发的。

不同之处在于，事件不是一次触发，而是多次触发(只要您按住键)。要意识到这一点，并相应地处理它们。

onkeypress事件适用于所有浏览器中除ALT, CTRL, SHIFT, ESC以外的所有键，其中onkeydown事件适用于所有键。意思是onkeydown事件捕获所有的键。

这篇由Jan Wolter撰写的文章是我所见过的最好的文章，如果链接失效，你可以在这里找到存档副本。

它很好地解释了所有浏览器键事件，

The keydown event occurs when the key is pressed, followed immediately by the keypress event. Then the keyup event is generated when the key is released. To understand the difference between keydown and keypress, it is useful to distinguish between characters and keys. A key is a physical button on the computer's keyboard. A character is a symbol typed by pressing a button. On a US keyboard, hitting the 4 key while holding down the Shift key typically produces a "dollar sign" character. This is not necessarily the case on every keyboard in the world. In theory, the keydown and keyup events represent keys being pressed or released, while the keypress event represents a character being typed. In practice, this is not always the way it is implemented. For a while, some browers fired an additional event, called textInput, immediately after keypress. Early versions of the DOM 3 standard intended this as a replacement for the keypress event, but the whole notion was later revoked. Webkit supported this between versions 525 and 533, and I'm told IE supported it, but I never detected that, possibly because Webkit required it to be called textInput while IE called it textinput. There is also an event called input, supported by all browsers, which is fired just after a change is made to to a textarea or input field. Typically keypress will fire, then the typed character will appear in the text area, then input will fire. The input event doesn't actually give any information about what key was typed - you'd have to inspect the textbox to figure it out what changed - so we don't really consider it a key event and don't really document it here. Though it was originally defined only for textareas and input boxes, I believe there is some movement toward generalizing it to fire on other types of objects as well.