Use custom NoAutofill field to avoid password manager issues#1763
Merged
alexbakker merged 1 commit intobeemdevelopment:masterfrom Jan 21, 2026
Merged
Conversation
alexbakker
approved these changes
Jan 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We've received reports that sometimes the Google Password Manager popup would show up when (manually) editing the Secret within an TOTP entry. This popup asks the user whether the secret value should be used as password for Aegis. When the user accidentally clicks on 'Yes', their master password used for unlocking the vault will get overwritten by the TOTP secret.
Since the AutofillServices are a pain the ass to deal with I had to use our custom TextInput which completely disables all autofill features.
Example:
