I'd add that the expected sequence of events is `keydown`, `selectionchange` – that's because in normal environments if you `preventDefault()` the `keydown`, then `selectionchange` isn't fired at all.

So, one thing would be making Android consistent with itself and always firing these two events in the same order.

The other thing is that we'd love if `selectionchange` was fired after `keydown`.

Please use "beforeInput" event[1] instead of keydown.
There are no guarantees about event sequence with Keyboard events from IME.
Also, in Android IME framework, the button looks like "Backspace" doesn't
sometimes generate keyboard event since keyboard apps uses different API
to remove contents.


[1] https://www.w3.org/TR/input-events-2/

Thanks for the details. We're aware of the fact that Android IME makes it impossible for you to fire keydown events with keyCodes. However, I think that we never saw keydown not being fired at all. Am, I right @k.krzton? Does it happen only with some types of Android keyboards, @yosin?

Another thing is the order of events – I understand that Android IME works by applying high-level operations to the edited content. Does it also mean that the browser is not able to translate that into a consistent order of selectionchange and keydown? It's unnatural if keydown is fired after selectionchange. If you kinda "mock" this event, can't you mock it earlier?

Finally, I thought that beforeInput is still not available on Android, but maybe we checked it too long time ago. I had quite good results when working on https://github.com/w3c/editing/issues/149 initially so we'll see. Thanks for the tips.

Yes, I have never seen `keydown` not being fired at all, but I didn't tested different keyboards than the default ones so maybe that's the case (still I assume custom keyboards may results in many different/strange behaviours).

As for `beforeinput` it looks like it is not available on Chrome `67.0.3396.87` on Android `6.0.1`  (tested on https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html). @yosin is there any specific version of Android from which `beforeinput` should work?

> There are no guarantees about event sequence with Keyboard events from IME.

@yosin, so the order of event like `key*` is not guaranteed, but for `input` and `beforeinput` (if it's there) you can always expect to have consistent order, is that right?

AFAIK, GBoard (Google keyboard) and some CJK keyboards don't dispatch "keydown" for Backspace.

For CJK keyboards, during text composition, keyboard events are vary in each implementation and unpredictable.


"beforeinput" was implemented on April 2016[1]. I'm not sure exact version.
It seems at least Chrome 53, released on August 30, 2016.

 https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html has a bug to
support "beforeinput", please change |function init()| as below:

function init() {
...
	addEventListener(input, "textinput", onTextInput);	// For IE9
	addEventListener(input, "beforeInput", onBeforeInput);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~beforeinput // "Input" -> "input"
	addEventListener(input, "input", onInput);
...
}


>for `input` and `beforeinput` (if it's there) you can always expect to have consistent order, is that right?
Yes. "beforeinput" is always dispatched before "input".
Note: "beforeinput" is dispatched before "compositionupdate".

[1]  http://crbug.com/585875  Support for Input Events

Thanks for clarification @yosin! Yes, I have noticed there is `beforeInput` instead of `beforeinput` in https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html after posting my comment and retested it on https://jsfiddle.net/f1ames/gLce925n/ - now I can see there is indeed `beforeinput` event fired.