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
When 'Autospace after punctuation' is turned on, the use of the phantom space seems to break with the particular use case where you hit shift to create a capital letter. The space will not be inserted when you start typing. This is particularly irksome in cases where you need to type 'I' after a comma, such as in this example: "However, I feel disheartened."
To Reproduce
Have 'Autospace after punctuation' turned on.
Open any text editor and type some words, then add a comma (,), then shift for capital letters and enter a key. A way of doing this would be to recreate the short sentence "However, I feel disheartened." Without editing the output, it will result in the following: "However,I feel disheartened."
Expected behavior
The space after the comma should be inserted, regardless of pressing shift.
App version
Version 2.3
Device:
Model: Motorola Moto G75
OS: Android 14 (not modified)
The text was updated successfully, but these errors were encountered:
Bug description
When 'Autospace after punctuation' is turned on, the use of the phantom space seems to break with the particular use case where you hit shift to create a capital letter. The space will not be inserted when you start typing. This is particularly irksome in cases where you need to type 'I' after a comma, such as in this example: "However, I feel disheartened."
To Reproduce
Have 'Autospace after punctuation' turned on.
Open any text editor and type some words, then add a comma (,), then shift for capital letters and enter a key. A way of doing this would be to recreate the short sentence "However, I feel disheartened." Without editing the output, it will result in the following: "However,I feel disheartened."
Expected behavior
The space after the comma should be inserted, regardless of pressing shift.
App version
Version 2.3
Device:
The text was updated successfully, but these errors were encountered: