Desktop - Chat - Sending a misspelled word doesn't return autocorrected and doesn't highlight

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Issue found when executing PR #10457

Action Performed:

1. Open the Expensify Desktop app
2. Sign into a valid account
3. Open any chat
4. Type missed spell word that the spell checker actually highlights
5. Wait for spellcheck to turn into a blue color word (First issue here)
6. Now send immediately with the blue color word (Second issue here)

Expected Result:

You will notice that it will replace missed spelled words and keep the auto-correct word after the message sent

Actual Result:

The misspelled word will underline red, however it will not highlight "blue" by itself, the user has to click on top of the word to activate this. Also, after sending the word that is highlighted blue it does NOT auto-correct itself and will continue to display misspelled in chat

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.91.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5704286_Autocorrect_is_not_working_on_desktop.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @joelbettner (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[dhairyasenjaliya]

Hm i don't think this is an issue as spell check functionality is only validate in iOS not support for any other platform

[melvin-bot]

@joelbettner Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[joelbettner]

I agree that this isn't an issue. I'm going to close this for now. Perhaps we will come back to it later.