3 ms·
It wasn't the Grammarly extension, it was the desktop app.
by saulpw 3y ago
It wasn't the Grammarly extension, it was the desktop app.
- chatmasta 3y agoI guess I just assumed the extension was installed too, and communicating with the desktop app. But now I see the post doesn't mention the extension. If it was triggered even without the presence of the extension then that's quite strange, and even more suspicious - is that gif triggering a call to a localhost endpoint? Is the grammarly desktop app interacting with browser elements without using the extension? (IIRC the grammarly app uses some accessibility privileges to inject into textareas across all apps) Grammarly is honestly insane, I can't believe corporations allow it to run on employee machines.
- nonethewiser 3y ago> Is the grammarly desktop app interacting with browser elements without using the extension? (IIRC the grammarly app uses some accessibility privileges to inject into textareas across all apps) It seems like that must be the case. If we have the details right about desktop app only (which seemed pretty clear).