Spell checker corrections are off by 1 when emojis are present
Reported by
alex.sav...@gmail.com,
Feb 13 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3346.0 Safari/537.36 Steps to reproduce the problem: This opportunity was just too good to pass up, so here's the appropriate meme: https://goo.gl/vAqukA. Anyway, this is the working case: `I unfotunetly won't ...`. As expected, it gets corrected to `I unfortunately won't ...`. However, add an emoji anywhere before like so: `😁 I unfotunetly won't ...` and it suddenly shows the squiggly lines at `start - 1..end - 1` and corrects the sentence to `😁 Iunfortunatelyy won't ...`. Unfortunate, wouldn't you say? 😆 What is the expected behavior? What went wrong? Spell checker is borked. Did this work before? N/A Chrome version: 66.0.3346.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 29.0 r0
,
Feb 15 2018
Thanks for filing the issue! @Reporter: Could you please let us know if you are facing the issue any particular site. Any sample test URL/File shared with us, where spellcheck isn't working helps us to triage the issue in a better way.
,
Feb 15 2018
Any site, example: https://bugs.chromium.org
,
Feb 15 2018
Thank you for providing more feedback. Adding requester "vamshi.kommuri@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
,
Feb 20 2018
Unable to reproduce this issue on reported version 66.0.3346.0 and on latest canary 66.0.3350.0 using Windows 10 with steps mentioned above. Attaching screencast for reference. 1. Pasted 😁 I unfotunetly won't ... in comment field. 2. Red underline is seen under mis-spelled word unfotunetly. Now right clicked and selected unfortunately from suggestion. 3. Observed 😁 I unfortunately won't ... . @Reporter: Please check the video and let us know if we miss anything. If possible please guide us with a video on how to reproduce this issue. This info woud help in further triaging of the issue. Thanks!
,
Feb 20 2018
That's really weird since I followed exactly the same steps.
,
Feb 20 2018
Bingo! I figured it out: if you enable "Use a web service to help resolve spelling errors," then things will break. (It's disabled by default)
,
Feb 20 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 21 2018
Able to reproduce this issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #66.0.3346.0 and latest canary #66.0.3350.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
May 15 2018
Any updates?
,
Jul 2
Issue 857594 has been merged into this issue.
,
Jul 2
Friendly ping...! As the reporter raised a new issue (...comment#11)Hence requesting someone from "UI>Browser>Language>Spellcheck" team to have a look into this and help in further triaging it. Thanks!
,
Sep 18
,
Sep 18
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by ajha@chromium.org
, Feb 14 2018Labels: Needs-Triage-M66