Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Autocomplete on contenteditable divs with android default keyboard is behaving strangely when backspacing a word

  • 2 Antworten
  • 1 hat dieses Problem
  • 16 Aufrufe
  • Letzte Antwort von flyingcube

more options

I am developing a mobile web app that makes heavy use of contenteditable divs, and firefox android's behavior when typing in them has changed recently in how it handles autocomplete.

I have found this behaviour on sites other than my own, and have created a jsfiddle at http://jsfiddle.net/wEyh5/4/ where this can easily be seen. What happens is that when a word in the element is beginning to be deleted, autocomplete will insert the word that is being deleted at the beginning of the word (so start turns into starstart). I have noticed that this does not happen when using the swype keyboard, only the default android keyboard does this. On other browsers, autocomplete in contenteditable elements works fine.

Also, autocomplete and backspace perform as expected on input elements and other ways of entering text that I have tested so far. This problem happens on both firefox 17 and 18. Is there some way to make firefox mobile have consistent keyboard behaviour on contenteditable elements?

I am developing a mobile web app that makes heavy use of contenteditable divs, and firefox android's behavior when typing in them has changed recently in how it handles autocomplete. I have found this behaviour on sites other than my own, and have created a jsfiddle at http://jsfiddle.net/wEyh5/4/ where this can easily be seen. What happens is that when a word in the element is beginning to be deleted, autocomplete will insert the word that is being deleted at the beginning of the word (so start turns into starstart). I have noticed that this does not happen when using the swype keyboard, only the default android keyboard does this. On other browsers, autocomplete in contenteditable elements works fine. Also, autocomplete and backspace perform as expected on input elements and other ways of entering text that I have tested so far. This problem happens on both firefox 17 and 18. Is there some way to make firefox mobile have consistent keyboard behaviour on contenteditable elements?

Alle Antworten (2)

more options

Please check Firefox beta in the market or Nightly from https://nightly.mozilla.org there have been several keyboard changes in these builds.

more options

I just tested it on the firefox beta and it is working fine.