I hope the post is fair. Let me know if it isn’t. Our goal is to explain the situation to our customers, and help make other teams aware that their apps may be suffering similar issues.
Thanks to your debugging video pinpointing the issue, we have been able to fix it. There was a bug where Grammarly would try to poke nodes outside of the input field in certain cases. It should be fixed now in the latest version of Grammarly for Chrome – please check it out and let me know if it helped.
Can’t wait to let our customers know :)
[1] https://github.com/facebook/draft-js/issues/616#issuecomment...