android: 'text-change' event not firing until much much later, unless you press new line, space or period (only on g-board)

[joshoconnor89]

Steps for Reproduction

1. Use android emulator
2. add 'text-change' callback:

quill.on("text-change", () => {
  callContentCallback({
    content: JSON.stringify(quill.getContents()),
    source: null,
  });
  getTextCallback({
    content: JSON.stringify(quill.getText()),
    source: null,
  });
});

3. being typing, notice text-change does not get fired
4. HOWEVER, when tapping new line, period, or space, text-change WILL fire.

**UPDATE:

• 'text-change' does fire when typing letters, but ONLY if you type, and wait 5-10 seconds. its EXTREMELY SLOW. however, its instant when tapping a period, new line, or space.

**UPDATE #2 -Looks like it happens only with g-board third party keyboard, with the samsung keyboard it works great

Expected behavior: -Text change event should be called everytime a user inputs text

Actual behavior: -nothing happens

Platforms: -android

Include browser, operating system and respective versions

[gravataLonga]

So, there are zero any resolution about this? I'm getting same bug when using it in chrome. Exactly same.

[kaycbas]

I'm also getting this issue.

[xsonic]

+1

[Suryasai130499]

+1

[gravataLonga]

No resolution? Just a curioso note, this isn't happening only in android emulator. It can happen in normal browser like Chrome.

[gravataLonga]

Probably related with this issue: #3633

[pedrovgs]

I'm facing the same issue and this is only reproducible on Android. Chrome and Samsung Internet are both reproducing the same bug. It only happens when the editor is empty. If you fill programmatically the editor instance with some content, it works as expected.

[pedrovgs]

I've found a workaround for this. Handling the virtual keyboard manually. If you configure quill to manage the virtual keyboard manually, then the bug is not reproduced anymore. However, you'll have to handle the keyboard by yourself and the hide function doesn't work. I reported this bug to google already.

    const quillRoot = editor.root;
    quillRoot.setAttribute("virtualkeyboardpolicy", "manual");

[pedrovgs]

Keep in mind if you configure virtualkeyboardpolicy to manual, due to a bug in chromium only English virtual keyboard will work 😢

[dr-zr]

@pedrovgs did you manage to find another workaround for this? I'm experiencing the same issue :/