Re: [w3c/uievents-key] Implementation report (#45)

I had a look at the implementation report. WebKit now supports `KeyboardEvent.key`[1]. It's shipped in Safari too[2]. Here's my manual test results in Safari 11.0.3 on 10.13.3:

* In Unnamed key Attribute Values, all `key` attribute values are supported.

* In Standard Named Keys, I'm not sure how to test "Unidentified".

* In Modifier Keys, `key` attribute values other than "AltGraph", "NumLock", and "ScrollLock" are supported. My keyboard does not contain these three keys so I'm not able to test them.

* In Whitespace Keys, all `key` attribute values are supported.

* In Navigation Keys, all `key` attribute values are supported (some of them are emulated by fn + various keys on the keyboard).

* In Editing Keys, "Backspace" and "Delete" are supported. Not sure about "Insert".

* In UI Keys, "Escape" is supported. I don't have other keys.

* I haven't tested Device Keys because of the lack of the "PrintScreen" key.

* In General-Purpose Function Keys, all `key` attribute values are supported.

* I haven't tested Editing and IME Named Keys because of the lack of these keys.

* In Device-specific Named Keys, "Fn" is not supported (in all three browsers on macOS). Not sure about other keys (including Modifier Keys, Legacy modifier keys, UI Keys, Device Keys, General-Purpose Function Keys, Multimedia Keys, Multimedia Numpad Keys, Audio Keys, Speech Keys, Application Keys, Browser Keys, Mobile Phone Keys, TV Keys, and Media Controller Keys) because of the lack of these keys/devices.

I don't have a Windows machine and therefore I'm not able to provide the test results for Microsoft Edge.


-----

Test code:

```javascript
window.addEventListener("keydown", function (event) {
    let out = "KeyboardEvent: key='" + event.key + "' | code='" + event.code + "'";
    console.log(out);
}, true);
```

-----

Links:

[1] https://bugs.webkit.org/show_bug.cgi?id=36267
[2] https://webkit.org/blog/6987/release-notes-for-safari-technology-preview-15/

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents-key/issues/45#issuecomment-369193369