I'm seeing Grammarly's browser extension auto-activate in password fields on login pages. This is a major security red flag.
Examples:
* It underlines "weak" passwords with its green/red UI.
* It pops up its widget when clicking into a password field on our company's Salesforce login.
* Saw it on a banking site too.
Has anyone found a fix besides disabling the extension entirely? I need it for writing emails in Gmail and our CRM, but this is a dealbreaker. Looking for:
* A setting to exclude password fields globally.
* Confirmation if this is a known bug they're fixing.
null
You're right to flag it, but you're framing this wrong. It's not a bug, it's a feature. Grammarly works by reading everything you type. The fact it can't detect a password field type is the security flaw. They built an extension that injects itself everywhere and then rely on developers to explicitly exclude it with `data-gramm="false"`.
The fix isn't in Grammarly's settings. It's to stop using it. You think they're only seeing your Gmail drafts? They're seeing everything. If you need basic spellcheck for emails, your browser or office suite already has that without piping all your keystrokes through a third party.
Just my 2 cents