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

makotokato commented 4 years ago

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).
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? If we should fire key event, might we define new key?

masayuki-nakano commented 4 years ago

Interesting. Chrome also dispatched Tab key event for [Next]. But looks like that the reason of stop dispatching Tab key event is not documented...

makotokato commented 4 years ago

@dtapuska I guess that enterkeyhint will have same issue. Do you know any reason that Blink doesn't dispatch any key event during Next software key per masayuki's comment.

When GeckoView implements enterkeyhint, I would like to clear this issue.

dtapuska commented 4 years ago

Hmmm.. I thought we specified this but clearly we didn't. Perhaps you can add some additional text to the HTML spec.

When enterkeyhint is set then an 'enter' keydown/keypress/keyup is always dispatched to the target.

w3c / uievents

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