Element: keyup event

فهرست فصل‌ها دانلود آرشیوناشر

MDN Web Docs · نسخهٔ df622a2a1c1e · CC BY-SA 2.5 و مجوز جداگانهٔ ناشر برای نمونه‌کد

{{APIRef("UI Events")}}

The **keyup** event is fired when a key is released.

The [keydown](/en-US/docs/Web/API/Element/keydown_event) and keyup events provide a code indicating which key is pressed, while keypress indicates which character was entered. For example, a lowercase "a" will be reported as 65 by keydown and keyup, but as 97 by keypress. An uppercase "A" is reported as 65 by all events.

The event target of a key event is the currently focused element which is processing the keyboard activity. This includes: {{HTMLElement("input")}}, {{HTMLElement("textarea")}}, anything that is [contentEditable](/en-US/docs/Web/HTML/Reference/Global_attributes/contenteditable), and anything else that can be interacted with the keyboard, such as {{HTMLElement("a")}}, {{HTMLElement("button")}}, and {{HTMLElement("summary")}}. If no suitable element is in focus, the event target will be the {{HTMLElement("body")}} or the root. The event bubbles. It can reach {{domxref("Document")}} and {{domxref("Window")}}.

The event target might change between different key events. For example, the keydown target for pressing the <kbd>Tab</kbd> key would be different from the keyup target, because the focus has changed.

Because the event fires after the key is released, modifier-key properties ({{domxref("KeyboardEvent/ctrlKey", "ctrlKey")}}, {{domxref("KeyboardEvent/altKey", "altKey")}}, {{domxref("KeyboardEvent/shiftKey", "shiftKey")}}, and {{domxref("KeyboardEvent/metaKey", "metaKey")}}) reflect the state after release. For example, ctrlKey is false on the keyup event for the <kbd>Control</kbd> key itself. If another key is released while the <kbd>Control</kbd> key remains pressed, ctrlKey is true on that key's keyup event.

Syntax

Use the event name in {{domxref("EventTarget/addEventListener", "addEventListener()")}}:

js-nolint
addEventListener("keyup", (event) => { })

Alternatively, assign to the event handler property of the interface:

js-nolint
onkeyup = (event) => { }

Event type

A {{domxref("KeyboardEvent")}}. Inherits from {{domxref("UIEvent")}} and {{domxref("Event")}}.

{{InheritanceDiagram("KeyboardEvent")}}

Examples

addEventListener keyup example

This example logs the {{domxref("KeyboardEvent.code")}} value whenever you release a key inside the {{HtmlElement("input")}} element.

html
<input placeholder="Click here, then press and release a key." size="40" />
<p id="log"></p>
js
const input = document.querySelector("input");
const log = document.getElementById("log");

input.addEventListener("keyup", logKey);

function logKey(e) {
  log.textContent += ` ${e.code}`;
}

{{EmbedLiveSample("addEventListener_keyup_example")}}

keyup events with IME

Since Firefox 65, the [keydown](/en-US/docs/Web/API/Element/keydown_event) and keyup events are now fired during {{glossary("Input method editor")}} composition, to improve cross-browser compatibility for CJKT users (Firefox bug 354358). To ignore all keyup events that are part of composition, do something like this:

js
eventTarget.addEventListener("keyup", (event) => {
  if (event.isComposing) {
    return;
  }
  // do something
});

توجه: Unlike keydown, keyup events do not have special {{domxref("KeyboardEvent/keyCode", "keyCode")}} values for IME events. However, like keydown, compositionstart may fire _after_ keyup when typing the first character that opens up the IME, and compositionend may fire _before_ keyup when typing the last character that closes the IME. In these cases, isComposing is false even when the event is part of composition.

Specifications

{{Specifications}}

Browser compatibility

{{Compat}}

See also

  • [input](/en-US/docs/Web/API/Element/input_event)
  • [keydown](/en-US/docs/Web/API/Element/keydown_event)
  • [keypress](/en-US/docs/Web/API/Element/keypress_event)