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
I've done a few experiments and almost got it working but it seems that a direct approach won't work. Keyboards on mobile devices behave differently from their desktop counterparts - they don't send raw keycodes but instead they buffer text being edited and replace it on various occasions (depending on the system, keyboard and version of the keyboard) - case for Android is here: https://code.google.com/p/chromium/issues/detail?id=118639 . Sometimes they behave in a way called "dumb IME" - only then keys can be intercepted in a standard manner. There is no way to check if keyboard is a dumb IME or ask it to behave like such.
Once more pressing features are done, the way mobile will be implemented is going to rely on gestures (dragging, swiping, long-pressing and tapping) for most common actions (swapping, deleting, editing and changing todo-states) and a toolbar with the less common ones.
I can edit on my mobile, but I can not get my keyboard unless I click to edit, so I can not use [1]...[6] or [p] etc.
Could this be made available somehow on a mobile / tablet device?
The text was updated successfully, but these errors were encountered: