- From: Psychpsyo (Cameron) <notifications@github.com>
- Date: Tue, 09 Dec 2025 04:43:08 -0800
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 9 December 2025 12:43:12 UTC
Psychpsyo created an issue (w3c/uievents#406) https://w3c.github.io/uievents/#event-type-keydown says that > If the key is the Enter or Space key and the current focus is on a state-changing element, the default action MUST be to dispatch a [click](https://w3c.github.io/uievents/#click) event, and a [DOMActivate](https://w3c.github.io/uievents/#domactivate) event if that event type is supported by the [user agent](https://infra.spec.whatwg.org/#user-agent). This happens in all browsers.<sup>1,2</sup> The problem is that Firefox does not set the `ctrlKey` and `shiftKey` attributes on the dispatched click event. Webkit and Chrome<sup>1</sup> do. I think it makes sense for them to get set, though the spec should probably make that explicit. Also all the other modifier key attributes that apply to both keydown and click events. (might be worth checking whatever Webkit/Chrome do for a list.) <sup>1</sup> Chrome does not dispatch the click event if Ctrl is being held down. <sup>2</sup> I did not check for the DOMActivate event, as I am only interested in the click event. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/406 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/406@github.com>
Received on Tuesday, 9 December 2025 12:43:12 UTC