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
The element we are using is display: inline and contentEditable: true.
It seems that on inline display elements, the Google keyboard is mucking up the typing as it goes. This is a known issue among WYSIWYG editing attempts on Android:
The workarounds to try and allow this seem to be too much. It may just be that on Android, we force single-line input to be inline-block unless you have a supported keyboard (like Hacker keyboard) running.
The text was updated successfully, but these errors were encountered:
The element we are using is
display: inline
andcontentEditable: true
.It seems that on inline display elements, the Google keyboard is mucking up the typing as it goes. This is a known issue among WYSIWYG editing attempts on Android:
ianstormtaylor/slate#725
https://docs.google.com/document/d/1Hex89Di-r-Wfpo1DLAtxpetoX588ziXVoNyC87Je3Xc/edit#
People ask for easy fixes but there do not seem to be any:
https://stackoverflow.com/q/68187400/
https://stackoverflow.com/questions/12243592/how-to-disable-suggestions-when-in-content-editable-webview-android
The problem relates to Gboard's sending of key messages. They don't want to send normal keyup/keydown and consider this as "won't fix":
https://bugs.chromium.org/p/chromium/issues/detail?id=809107
Also, contenteditable is known to be annoying and on Android it's worse:
https://discuss.prosemirror.net/t/contenteditable-on-android-is-the-absolute-worst/3810
The workarounds to try and allow this seem to be too much. It may just be that on Android, we force single-line input to be
inline-block
unless you have a supported keyboard (like Hacker keyboard) running.The text was updated successfully, but these errors were encountered: