Fwiw, haven't been able to repro in any other app or any other website, but Kyle_Bennett (website owner) says there hasn't been any recent changes on the site, and he can't repro on his phone.

Issue persists through reboot. 

Tested the issue using #64.0.3282.137 on Android Samsung J7 7.0.0 and could not reproduce the issue as per the steps mentioned in original comment.

@benjo: Could you please check this issue in latest Chrome #64.0.3282.137 and help us with the details of your device and a screencast for further triage?

Thanks!!

Can't do the screencast atm, but will asap. Still present in 64.0.3282.137 for me. 

What details do you need aside from what I provided in the original report? I listed the language (en), keyboard (SwiftKey), phone model (Xperia XA, specifically F3113), Android version (7.0 Nougat).

The kernel is 3.18.35+

Seems like maybe a race condition causes this, as it's not always the first character in the word that is replaced in the input box. It may be a combination of SwiftKey, chrome, and hardforum specifically which trigger the race condition (seems likely, although I don't know how much each contributes). If you have an older phone you can install Android 7 and SwiftKey on to test with, you might have better luck reproducing. 

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Here's a video showing the issue on the affected website:
https://photos.app.goo.gl/ertKpLCUfcVRINDH2

This report references a forum using XenForo (1.x). I am a XenForo developer and we've had reports of this affecting many of our customers: https://xenforo.com/community/threads/latest-android-chrome-keyboard-suggestion-issues.142504/ Reports first started with Chrome 64.

I have been able to reproduce this issue and have derived a reduced test case. Specifically, it appears to related to contenteditable being initialized within an iframe (rather than directly on a div).

The reduced test case can be seen here: https://xenforo.com/bugs/android-rte-autocomplete-bug.html (Same code is also attached.)

The steps to reproduce are not 100% consistent and the behavior may vary by keyboard, but I can reproduce odd behavior in both Swiftkey and Gboard.

(Using Swiftkey) Type "Tym" and you'll likely get "Tympanum" and "Tympanic" suggested. Tap either of those. In the iframe case, sometimes the inserted text will be "TymTympa "; if it inserts correctly, empty the editor and try again. In the div version, the correct word will always insert.

(Using Gboard) Type "Trdt" and the recommendation should be "Test". Tap that and some of the time it will work; other times it will effectively do nothing. It seems much more inconsistent. Again, on the div version, this will work correctly in all cases.

As further evidence, similar steps cause issues with TinyMCE's demo: https://www.tinymce.com/ (Which still uses an iframe)

(All tests done in Chrome 64.0.3282.137 / Android 7.0 / Galaxy S6.)

Deleted: android-rte-autocomplete-bug.html 710 bytes

android-rte-autocomplete-bug.html 710 bytes View Download

Can confirm, reduced test case (hosted at xenforo, in comment 7) can repro on 64.0.3282.137. Odd behavior in iframe, expected behavior in div.

Cannot reproduce in Firefox mobile or Edge mobile (for Android). 

Seems fixed with SwiftKey v6.7.8.25 released March 1st.
Release notes:
Fixed 
* Previously jumbled words in Chrome should now display correctly  
* The longpress pop up box should now display on the screen

Hrm, well, mostly fixed. Very rarely it still puts a space character instead of a punctuation mark (? or ! at least).

I will notify the SwiftKey devs and mention this bug and related xenforum thread. 

Closing this issue as per comment #10. Please feel free to reopen if you see this again.

Thanks!!

This is still an issue as I'm having the exact same behavior in websites when using Google Chrome on my Google Pixel. V. 68.0.3325.109

What? This is not fixed at all. Writing is still broken in Xenforo forums on Chrome for Android using Gboard.

This issue is still present in GBoard. Yes it is fixed for SwiftKey but on Pixel it uses GBoard.

This is still a problem on my S8 using the Gboard in Chrome. Please fix.

This is still happening as of today. Proof:

Deleted: screenrecorder.20180902163703.mp4 11.4 MB

	screenrecorder.20180902163703.mp4 11.4 MB View Download

I still have the issues as well.

Problem still exists with the latest version of SwiftKey and Chrome on the S9