[w3c/uievents] Should Key event be fired for [Previous] and [Next] key on Virtual Keyboard? (#253)

Virtual Keyboard sometimes change [ENTER] key with [Done], [Search], [Previous], [Next] and etc on <input> element. See https://developer.android.com/training/keyboard-input/style.html for image.

[Done] and [Search] will fire ENTER key on all browsers (Safari/iOS, Chrome/Android and Firefox/Android). But [Previous] and [Next]'s behaviour is different.

- Chrome/Android doesn't fire any keyboard event for [Previous] and [Next] (I guess that souce code is [here](https://cs.chromium.org/chromium/src/content/public/android/java/src/org/chromium/content/browser/input/ImeAdapterImpl.java?type=cs&q=performEditorAction&sq=package:chromium&g=0&l=744)). 
- Firefox/Android emulates as another key ([Next] is TAB key), so it fires keydown as TAB and keyup as TAB.
- Safari/iOS doesn't change [ENTER] with [Previous] and [Back]. So we can ignore this.

Should Key event be fired for [Previous] and [Next] key on Virtual Keyboard? Or not?

-- 
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/253