We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I have word prediction turned on on Android, the app writes each letter in a own line like: H e l l o
There is another bug when I turn auto correction off and I start a new note the first letter gets a space like: "H ello"
My device is running on CyanogenMod 13 and use the RC1 apk for Android
The text was updated successfully, but these errors were encountered:
Seconded. I get this exact bug on a 2013 Nexus 7 running stock Android 6.0.1, using android-armv7-release.apk 0.7.4-RC1.
Sorry, something went wrong.
This screenshot shows what happens if I enter the string "singlewordnospaces":
This is what happens if I enter the string "sentence with normal spaces":
Swype-style entry (still using the native Google keyboard) works fine, but that's not a viable workaround for proper names, abbreviations, etc:
Same here with marshmallow. While adding tags I noticed sometimes # adds a trailing whitespace also.
I have an other bug related to this I think, it's when I edit a word : type [] doar remove a [] dor type o and the a reappear : [] dooar
[] doar
[] dor
[] dooar
When I did it I saw that on some other lines of my list, after all of the emoji, some squared question mark appeared.
I cannot add or edit my grocery list because of his bug, please fix it
No branches or pull requests
When I have word prediction turned on on Android, the app writes each letter in a own line like:
H
e
l
l
o
There is another bug when I turn auto correction off and I start a new note the first letter gets a space like: "H ello"
My device is running on CyanogenMod 13 and use the RC1 apk for Android
The text was updated successfully, but these errors were encountered: