Next word prediction should honor shift cycle
What would you like?
Next word predictions on the suggestion bar should honor the current state of the shift cycle. Currently, they always stay in lowercase in the middle of the sentence and in first letter capital at the start of the sentence.
Why it would help
This would improve user’s typing experience by eliminating additional steps to change the casing of the word after the fact.
Discussion
Sign in to comment or vote.
@ilikered done in build 428, and it'll be in 2.1.3 on the App Store. After a space the predictions now follow shift: shift on gives "Test", caps lock gives "TEST", and the bar updates as soon as you toggle it. Tapping inserts exactly what the bar shows. Words that already have their own casing, like iOS or I'm, stay as they are. The sentence-start words in an empty field (The / I / I'm) also go lowercase now when you turn shift off.
At the sentence start:
Only "the" honors the case cycle, I and I’m honors only first letter upper and all upper, not lower.
When I type one letter and try shift cycle, the predictions don’t change casing. Also noticed that at the start of the sentence, when we type the first letter in capital, we cannot change it back to lowercase through shift cycle. These two maybe related.
Mid sentence words:
When I type one letter and try shift cycle, the predictions only change between lowercase and first letter uppercase. All uppercase doesn’t work.
@ilikered fixed in build 429, and it'll be in 2.1.3 on the App Store. A single letter now cycles t → T → T with caps lock → t. The caps-lock step shows TEST in the bar and keeps the next letters uppercase until you hit space or pick a suggestion. Caps lock also applies to completions while you're typing a word, so "t" with caps lock on shows TEST too. At the start of a sentence a capital first letter can now be cycled down to lowercase. Shift stays on after that, so if you tap shift to write something like "SK" you still get "SK". I and I'm at the start of an empty field stay capitalized even with shift off. That one's intentional: a lowercase "i" is wrong in English, and autocorrect would turn it back into "I" when you commit anyway.
Looks good.
For I and I’m, with auto correct off, lowercase i stays lowercase. Hence a forceful lowercase conversion should be considered intentional. But I’ll leave it to you.