Comment 6 for bug 1646346

Olivier, I no longer have a device to test this on. However, I am fairly sure that this problem did occur in other "web apps" using the same "browser base" (oxide?). But if it is related to the keyboard, and autopunctuation, one would suspect it to be system wide.

Also, I remember that it seemed that it occurred when typing something really fast, as if the rapid input stream were able to overwhelm the autotype/error correction and punctuation "algorithm". As if it were taking in two white space chars and substituting them with a full stop, but before being able to update it's own "memory" of what currently exists. Then when the user goes back to erase the full stop, it would still think that this char is in reality two chars, and seek to erase both the replaced white space (now the full stop at the end of the sentence) and the preceding white space. In this state the first preceding white space would of course be *before* the word and therefore deleting this would appear to concatenate the two last words.

I was using "Finnish" with all the mentioned things active (spellchecking, auto word correction, word suggestion, auto uppercase and/or auto punctuation).