Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

first letter reapeted after writing a word, press ENTER and then backspace #920

Closed
e075e opened this issue Mar 5, 2017 · 6 comments
Closed
Milestone

Comments

@e075e
Copy link

e075e commented Mar 5, 2017

Steps to reproduce

  1. write a word, for instance "hello". Do not auto correct it or press the highlighted word on the suggestion bar
  2. press ENTER
  3. press BACKSPACE

Expected behaviour

word "hello" is displayed

Actual behaviour

word "hhello" is displayed

Android OS version:
4.4.1

Device manufacturer and model:
LG D620

List of installed add-ons (like languages, or themes):
English QUERTY Latin Keyboard
Italian querty + language pack

bug affected both layouts

@mtbu
Copy link

mtbu commented Nov 2, 2017

This happens to me using v1.8.1333 from F-Droid, on LineageOS 14.1 using English QWERTY layout.

@menny menny added this to the 1.9-r1 milestone Nov 9, 2017
@menny
Copy link
Member

menny commented Nov 20, 2017

I'm really having issues reproducing this. Sometimes I can make it will happen and sometimes backspace will behave correctly. I'm still trying to figure this out, but I might need to push that to a later release.

@tedkotz
Copy link

tedkotz commented Nov 21, 2017

I'm able to get very similar results with a build of master when using gesture typing. if I swipe in "this", It looks fine. if I hit any other letter say "d" then hit back space I get "tthis" with "this" underlined.

@mtbu
Copy link

mtbu commented Nov 22, 2017

I think it may depend what app is running, for instance it happens to me with com.simplemobiletools.notes (v2.3.0 from F-Droid)

menny added a commit that referenced this issue Nov 22, 2017
@menny
Copy link
Member

menny commented Nov 24, 2017

I think I found the issue, or at least, one of the issues. It's related to typing in apps that have a slow InputConnection implementation. It is not uncommon to see apps like that.

@menny
Copy link
Member

menny commented Nov 24, 2017

The fix will be available in the next ALPHA and BETA

@menny menny closed this as completed Nov 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants