You can tell it's not just you when suddenly your swipe text has randomly capitalized words. I get LoL _constantly_ since the beginning of this year, despite going back and rewriting it letter by letter every time for the first month or so it happened. I'm not sure I've ever typed it that way intentionally, as I don't play the game and neither do my friends.
Ever since Google changed the way they did autocorrect[1] a few years ago it's been pretty terrible and getting worse. There's random "words" that I can't remove from predictions[2] because at some point I used double dashes somewhere and Android remembered `not--it's` as a word itself[3]. Then there's words that I've had to explicitly add to my dictionary because despite using them frequently for a year (eg. CLI program names and options) just one time backspacing to change the ending of one was enough to remove it from whatever temporary memory is kept that's not part of the actual dictionary.
Desktop isn't much better. I actually somewhat like having the text inputs in some programs as I do writing in nontraditional programs (like arbitrary chat programs that don't implement spell check, because why would they?) but it feels incredibly unintuitive, especially when using RDP from my tablet [4], but also when using it locally. Windows is a keyboard-first OS for me, I shouldn't need to use the mouse for any first-party functionality.
1: including autocomplete suggestions, predictive text, and swipe input. I call all of these autocorrect since they mostly seen to share the same dictionary and rules.
2: they're not in my custom dictionary, and dragging the suggestion to the middle of the screen doesn't prevent it from happening again)
3: easy fix, but it needs to be implemented: a single dash is part of a word, a double dash is not.
4: this is an area Microsoft could improve tbh. They know what kind of input you're using when you're in edge or command line. In these software the mobile RDP client should provide keyboard hints to the local soft keyboard to switch input modes based on form input types, and should reset the local keyboard when the active remote keyboard context changes. It should certainly not be deleting entire command lines when I hit backspace in RDP (this is especially annoying in CMD and notepad) as the local software keyboard doesn't know that the my long string was 7 inputs to 4 different programs, not one long input.
Desktop isn't much better. I actually somewhat like having the text inputs in some programs as I do writing in nontraditional programs (like arbitrary chat programs that don't implement spell check, because why would they?) but it feels incredibly unintuitive, especially when using RDP from my tablet [4], but also when using it locally. Windows is a keyboard-first OS for me, I shouldn't need to use the mouse for any first-party functionality.
1: including autocomplete suggestions, predictive text, and swipe input. I call all of these autocorrect since they mostly seen to share the same dictionary and rules. 2: they're not in my custom dictionary, and dragging the suggestion to the middle of the screen doesn't prevent it from happening again) 3: easy fix, but it needs to be implemented: a single dash is part of a word, a double dash is not. 4: this is an area Microsoft could improve tbh. They know what kind of input you're using when you're in edge or command line. In these software the mobile RDP client should provide keyboard hints to the local soft keyboard to switch input modes based on form input types, and should reset the local keyboard when the active remote keyboard context changes. It should certainly not be deleting entire command lines when I hit backspace in RDP (this is especially annoying in CMD and notepad) as the local software keyboard doesn't know that the my long string was 7 inputs to 4 different programs, not one long input.