Samsung autosuggest skips first character after first word.

Eh … woah. No idea where to even begin here. Also, I don't have access to such a phone.

Without more detailed steps to reproduce, I doubt we'll ever be able to fix this one. For example: can you reproduce this using different browsers on the same phone?

I've been able to reproduce using Browserstack on a Samsung Galaxy S22 with Chrome browser. I did set the keyboard to Nederlands (I haven't actually checked if it is relevant yet, but might well be).

Yup, confirmed. I installed Drupal 10.2.2 on Simpytest.me and went to create an Article. When using the onscreen keyboard the issue is visible. In all honesty, I suspect this is at least in part an issue with the Samsung keyboard, but looks like it is exclusive to Drupal; I've tried confirming on https://ckeditor.com/ckeditor-5/demo/editor-types/ but it seems to be working fine there.

Tried to remove all the buttons from the editor on my Simplytest.me install. I had to keep a separator, Drupal wouldn't let me safe an empty toolbar. Still the issue.

Updated IS

I hesitate to add this to the issue summary, but there apparently *are* several issues with the Samsung keyboard. Just haven't found this particular one. But for example https://github.com/ckeditor/ckeditor5/issues/15584

Thanks for that detective work, @eelkeblok, much appreciated! 🤩

I had to keep a separator, Drupal wouldn't let me safe an empty toolbar. Still the issue.

This makes it 99% likely the problem is upstream, and that it only works on the official CKEditor 5 demo because of some additional plugin that is loaded there and not in Drupal that masks/accidentally fixes the problem 😅 Fascinating!

OK. That would warrant setting up a very simple test page with just the editor loaded. Thanks!

Testing with a limited editor downloaded from CKEditor.com suggests this is a Drupal issue after all. Will do more spelonking and playing with input filter settings to hopefully narrow it down.

Our next step will be setting up a minimal test with the specific version of CK that comes with Drupal.

By what was basically pure luck, I found an instance where the editor is running in Drupal, but the issue did not occur, so the process of elimination could start. I think I have it narrowed down to misc/form.js; when I suppress that (by basically just removing the file from the library defintion and clearing caches), I could "fix" the issue in the editor. Onto whatever is causing the problem inside that file...

Not sure if the jQuery stuff is the culprit, but I'd love to see what a jQuery-free implementation would do...

Keep up the good work! 👏

The customer has decided we are not going to continue debugging this, unfortunately. We've come a long way, though, maybe it helps others when they encounter this.