- From: Denilson Sá Maia <notifications@github.com>
- Date: Fri, 26 May 2023 14:17:09 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents/issues/347@github.com>
The [5.6.2. Keyboard Event Key Location](https://w3c.github.io/uievents/#events-keyboard-key-location) section ([source](https://github.com/w3c/uievents/blob/157ddf47c55f28d98615e8564e979b9959819bca/sections/event-types.txt#L2767-L2803)) has a table of several keys that have different locations, and a list of all the possible (and known) values for `.location` for such keys. It also says: > For all other keys not listed in this table, the [location](https://w3c.github.io/uievents/#dom-keyboardevent-location) attribute MUST always be set to [DOM_KEY_LOCATION_STANDARD](https://w3c.github.io/uievents/#dom-keyboardevent-dom_key_location_standard). However, the `Insert` and `Delete` keys are missing from that table. Those keys are traditionally together with Home/End and Page Up/Down; and they are also available as `Numpad0` and `NumpadDecimal`. Additionally, both Firefox and Chrome (on Linux) report `Insert` and `Delete` with `.location = 3` (`DOM_KEY_LOCATION_NUMPAD`), deviating from the current draft. Thus, I believe the lack of those keys in the UI Events spec was a mistake. (I have not tested on any other system.) You can test the behavior yourself by disabling NumLock and trying those keys on either https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html or https://codepen.io/denilsonsa/pen/epmoma -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/347 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/347@github.com>
Received on Friday, 26 May 2023 21:17:15 UTC