Why we parted ways with Grammarly (and you should too)

Why we parted ways with Grammarly (and you should too)(medium.com)

17 points by jmedwards 8 years ago | 7 comments

jgwhite 8 years ago |

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.

theblacktaxi 8 years ago | |

Hey Jamie, my name is Sergey and I'm a developer for the Grammarly extension. Sorry to see you had so much trouble with Grammarly! That definitely wasn't our intention – quite the contrary.

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.

0xADADA 8 years ago | | |

Sergey, I'm also running into this. Is there a way to prevent grammarly from running on our app from the code? An a css class, or <meta> tag we can add to opt-out?

jgwhite 8 years ago | | |

Fantastic. Thanks so much Sergey!

Can’t wait to let our customers know :)

codepodu 8 years ago | |

I've been in touch with Grammarly as well [1]. I work for a publishing platform with thousands of writers, editors and contributors. It was very difficult to tell people they can't use Grammarly :/

[1] https://github.com/facebook/draft-js/issues/616#issuecomment...

0xADADA 8 years ago |

Holy crap, i just got our first bug report about this exact same problem, Ember 2.14.

jgwhite 8 years ago | |

The latest version of the Grammarly extension resolved the problem entirely for us. Hope it does the same for you!