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 following bug occurs on android with both GBoard and Samsung Keyboard.
When predictive text/suggestion strip is toggled on in the keyboard settings, it will disable caps after a character conversion while entering katakana (with caps on).
So entering AMERIKA will result in アめりか as caps turns off after converting the first character. It does not do this for regular input fields, where typing AMERIKA will still result in AMERIKA rather than Amerika. Note that it does not matter if it's the very first character of the word or not, it does the same thing regardless of position inside the word.
I've also fiddled around with changing the autocomplete/spellcheck/autocorrect/autocapitalize attributes, but that didn't seem to change the behavior either.
Steps to reproduce
Go to wanakana.com and try the above on an android device with predictive text (samsung) or suggestion strip (gboard) setting toggled on in the keyboard settings. Somehow it keeps resetting the caps lock after a character conversion.
Versions
I'm using version 4.0.1.
Browser:
Tested with Chrome on Android, but I assume it happens in any browser.
OS/Device:
Android
Keyboard/Input Method:
Samsung Keyboard
GBoard
Possibly others?
The text was updated successfully, but these errors were encountered:
Issue Type
Description
The following bug occurs on android with both GBoard and Samsung Keyboard.
When predictive text/suggestion strip is toggled on in the keyboard settings, it will disable caps after a character conversion while entering katakana (with caps on).
So entering AMERIKA will result in アめりか as caps turns off after converting the first character. It does not do this for regular input fields, where typing AMERIKA will still result in AMERIKA rather than Amerika. Note that it does not matter if it's the very first character of the word or not, it does the same thing regardless of position inside the word.
I've also fiddled around with changing the autocomplete/spellcheck/autocorrect/autocapitalize attributes, but that didn't seem to change the behavior either.
Steps to reproduce
Go to wanakana.com and try the above on an android device with predictive text (samsung) or suggestion strip (gboard) setting toggled on in the keyboard settings. Somehow it keeps resetting the caps lock after a character conversion.
Versions
I'm using version 4.0.1.
Tested with Chrome on Android, but I assume it happens in any browser.
Android
The text was updated successfully, but these errors were encountered: