bug(windows): Backspace behaviour is wrong in QuillJS on Chrome/Windows (for example in Slack and linkedin.com)

[MakaraSok]

Describe the bug

Using Ma'di keyboard in Slack or linkedin.com to type certain sequences does not work output the expected characters.

Key sequence: a + . + / Expected output: ạ́ Actual output:

• Slack: (all character got erased)

• LinkedIn.com: ̣́

To Reproduce

1. Install Ma'di keyboard
2. Go to Slack or Linkedin.com
3. In the text box on Slack or post/comment on linkedin.com, type in a + . + /
4. See error

Expected behavior

ạ́ should be output consistently and globably.

---

Keyman for Windows:

• OS: Windows 10 Pro 20H2 x64
• Keyman version: 14.0.244-beta
• Target Application: Slack 4.13.0 64-bit and LinkedIn (Post and Comment sections) on Chrome v88.0.4324.190 (Official Build) (64-bit)

---

Keyboard

• Keyboard name: Ma'di
• Keyboard version: 1.0
• Language name: Ma'di

[mcdurdin]

Can you report on the Chrome version you are testing with? (... Help/About)

[mcdurdin]

This appears to be a bug in QuillJS, which is the editor used in LinkedIn and Slack.

There is not really a great workaround at this time in Chrome. Note that it seems to work well in Firefox 86.0 (which has fixed a few bugs in its handling of backspace and interactions with Keyman).

See my bug report at https://github.com/quilljs/quill/issues/3302

[mcdurdin]

quilljs/quill#3302 has been automatically closed with the release of quilljs 2.0 but there is no indication that the bug has been fixed. We need to retest with quilljs 2.0 and proceed accordingly.

[rc-swag]

The problem is no longer reproducible in the https://quilljs.com/playground/snow plaground however it still exists in both Slack and Linkedin.com.

I have raised the issue with Slack via the contact centre. There is no issue or bug number to track, unfortunately.

Linkedin I have a case number I can track under my login.

[rc-swag]

Reply from Slack Hi Ross,

Just wanted to provide you with an update on this bug you raised with us, regarding the diacritic deletion via Backspace:

Our Product and Engineering teams have evaluated this bug against factors of severity, impact, scale and frequency. With this in mind, we've made the decision to prioritize working on other issues with a greater known impact. As such, I’m afraid we won't be fixing this issue at this time.

That said, we're keeping an eye out for continued reports which could cause this decision to be revisited down the line.

Please do let us know if you have any questions. Otherwise, thank you again for taking the time to make this report.

[mryellow]

Thankyou for that professional response.

It's a breath of fresh air with everyone using bots to simply delete and hide all "stale" issues.