From f284719392aedaa4d11cd60dbaf1b3efb4769577 Mon Sep 17 00:00:00 2001 From: benignant <19580651+benignant@users.noreply.github.com> Date: Tue, 8 Oct 2024 16:04:49 -0400 Subject: [PATCH] Clarify note about keyboard-activated click events (#36256) --- files/en-us/web/api/element/click_event/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/element/click_event/index.md b/files/en-us/web/api/element/click_event/index.md index 2d4ed873ee6afb6..98ad287fe870fe7 100644 --- a/files/en-us/web/api/element/click_event/index.md +++ b/files/en-us/web/api/element/click_event/index.md @@ -15,7 +15,7 @@ An element receives a **`click`** event when any of the following occurs: - Any user interaction that is equivalent to a click occurs, such as pressing the Space key or Enter key while the element is focused. > [!NOTE] -> In practice, browsers don't fire the `click` event for custom controls such as a `
` with `tabindex="0"`. To check the reason behind this behavior, see this [Chromium issue](https://crbug.com/40776466). +> In practice, browsers don't fire the `click` event for custom controls (such as a `
` with `tabindex="0"`) when activated by keyboard. To check the reason behind this behavior, see this [Chromium issue](https://crbug.com/40776466). If the button is pressed on one element and the pointer is moved outside the element before the button is released, the event is fired on the most specific ancestor element that contained both elements.