You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[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?
The text was updated successfully, but these errors were encountered:
@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.
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.
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?
The text was updated successfully, but these errors were encountered: