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).
In particular, why is the following behaviour for
KeyboardEvent.key
specified when dead keys also are handled byCompositionEvent
?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).