Re:Why we parted ways with Grammarly (and you should too)
by theblacktaxi on Wednesday October 25, 2017 @07:47PM
(#15555278)
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.
Re:Why we parted ways with Grammarly (and you should too)
by 0xADADA on Thursday October 26, 2017 @04:52PM
(#15562902)
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?
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.