Skip to content

Stop flagging autofill-suppressed and look-alike fields as sensitive - #89

Merged
wolfiesch merged 2 commits into
mainfrom
fix/sensitive-field-false-positives
Oct 27, 2026
Merged

wolfiesch merged 2 commits into
mainfrom
fix/sensitive-field-false-positives

Conversation

@wolfiesch

Copy link
Copy Markdown
Owner

AgentTab refused to fill every text input on forms that set autocomplete="new-password" on plain text fields to suppress browser autofill (the Azure portal does this on every input), and it flagged labels that only contained a secret word as a substring ("residual" and "incident" both contain "cid").

  • autocomplete="new-password" alone no longer marks a field sensitive. Real new-password fields are still caught by type="password" or a password name.
  • Secret-name terms now match whole words only.
  • Still blocked: password inputs; current-password, one-time-code, webauthn, and cc-* autocomplete tokens; fields named for passwords, one-time codes, card data, or bank numbers.

Verification: new regression test fails before and passes after; bun run extension:check passes; a rebuilt extension filled an Azure portal text input that was previously refused.

autocomplete=new-password alone no longer marks a field sensitive; sites
use it on plain text inputs to suppress autofill. Secret names now match
whole words only, so labels such as 'residual' no longer match 'cid'.
@wolfiesch
wolfiesch merged commit b21168a into main Oct 27, 2026
9 checks passed
@wolfiesch
wolfiesch deleted the fix/sensitive-field-false-positives branch October 27, 2026 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant