Users report that the Grammarly for Safari extension does not work properly in Discourse input fields, particularly when replying to topics, despite functioning correctly on other websites. Justin_Vega initially identified the issue, noting that while Grammarly highlights errors, users cannot click them for suggestions. Others, like anon73664359 and valsha, confirmed the problem occurs across browsers, including Firefox, and that no console errors are present. pmusaraj claims it works fine for them, suggesting the issue might be isolated or browser-specific. After contacting Grammarly, anon73664359 was told the issue wasn’t on their end. However, Justin_Vega later reported that the issue resolved after a Discourse beta update, indicating the problem likely stemmed from Discourse itself rather than the extension.
There is this great Safari extension “Grammarly for Safari” that helps you to improve the text you write. It highlights grammar problems and makes suggestions on how to fix them or improve our text in other ways:
Unfortunately, this doesn’t work in Discourse input fields. The extension gets added to the input field and also highlights the problems, but you can’t click the highlights to get the suggestions. From my usage Discourse is the only location where this doesn’t work, so I assume Discourse is doing something that breaks this functionality.
I just installed Grammarly for Safari, and it seems to work fine. I made a few typos, Grammarly highlighted them, and clicking on the popup fixed the typos. This was in the composer. On regular input fields, Grammarly isn’t available at all.
Yes, strange behavior
When I am creating a new topic all is ok, when I am trying to reply to an existing topic, Grammarly is not working
I am using Firefox.
No issues for me on Safari 14.1.2 when writing this reply. @valsha you can try to see if there are errors in the Firefox console, but this works for me and as mentioned above this is 99% a Grammarly issue.
One of the forums I’m on just updated to the latest beta version of Discourse and the Grammarly extension for Safari now works fine.
I’m not sure if the issue will come back, but I think we can now safely confirm that this was an issue with Discourse, not the Grammarly extension for Safari.