Annoying, complex bug

Complex, requires multiple inputs. Not all inputs are nessarily relevant but in my limited experience they are interrelated.
1. Under certain conditions, perhaps most visible immediately after a keyboard pops up: The output is not processed for a significant fraction of a second. After this delay, all [buffered] inputs are reflected to the screen, all ticking sounds emmited close together. Then processing settles down.
2. Settings disable processing accents.
3. If a double ee is typed very rapidly, or at a hiatus [as in number 1 above], it may produce an accented e. Grave e?
4. If you are on a phone, small font, poor eyesight, etc., you stand a good chance to miss this "typo".

Is this serious? You bet. Combine this behavior with the typing dictionary, and such a typo can end up embedded in your dictionary and get propagated with no end. Have this happen to your login name, and you cannot get back into some Important accounts. Yuck!

If a human reads this, please let me know.

Sincerely
Simon Shapiro

Alpert

17 de maio de 2019 18:24

Hi Simon,

Sorry for the trouble.

1. What's your device name, android version, and SwiftKey version? What does "certain conditions" mean? We need more information to create the test environment.

2&3. I don't understand, any screenshot or screen recording to show the problem?

4. You can change the font size in your phone settings (if your device supports this), you can also increase the size of SwiftKey on-screen keyboard.