搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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

  • 2 回覆
  • 1 有這個問題
  • 16 次檢視
  • 最近回覆由 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?

所有回覆 (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.