[w3c/uievents] What's the rationale for the currently specified interaction between dead keys and `KeyboardEvent.key`? (#281)

In particular, why is the following behaviour for `KeyboardEvent.key` specified when dead keys also are handled by `CompositionEvent`?

> #### [§ 6.3.2. Dead keys](https://w3c.github.io/uievents/#keys-dead)
>
> [...]
>
> ##### Example 26
>
> [...]
>
>  In the second keydown event (step 5), the key value (assuming the event is not suppressed) will not be "e" (Latin Small Letter E key) under normal circumstances because the value delivered to the user agent will already be modified by the dead key operation. 

It seems to me (in my mildly uninformed opinion) that the OS APIs needed to only deliver "e" in `KeyboardEvent.key` exist on every major OS (except perhaps iOS, which I know nothing about).

-- 
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/issues/281