Quick Username Picker: Stop Retyping Your Email Every Time You Add a Login #18891
Replies: 2 comments
-
|
✨ Thank you for your code contribution proposal! While the Bitwarden team reviews your submission, we encourage you to check out our contribution guidelines. Please ensure that your code contribution includes a detailed description of what you would like to contribute, along with any relevant screenshots and links to existing feature requests. This information helps us gather feedback from the community and Bitwarden team members before you start writing code. To keep discussions focused, posts that do not include a proposal for a code contribution will be removed.
Thank you for contributing to Bitwarden! |
Beta Was this translation helpful? Give feedback.
-
Yes, I think so... no, doesn't seem like it... see this feature request here: https://community.bitwarden.com/t/autocomplete-default-username-random-password-when-creating-new-entries-or-option-in-generator/4150 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Abstract:
I want to propose a small feature that would save me from constantly retyping the same 2-4 email addresses when creating new login entries. Show me my recently used usernames as clickable suggestions in the "Add Login" form, and let me pick one with a single click instead of typing it out every time.
Why this matters
I manage multiple email addresses for different purposes: personal, work, shopping, throwaway accounts. Every time I sign up for a new service, I have to type out the full email address character by character. It's tedious when it happens constantly, and I find myself wishing I could just click "mario.rossi@personal.com" from a list instead of typing it for the hundredth time.
The workflow would be simple: focus on the username field, see your 3-4 most recent usernames in a dropdown, click one to auto-fill. If you start typing, it filters the list. That's it.
Security and implementation
The username list would be encrypted using Bitwarden's existing crypto patterns. Store it as an EncString encrypted with the user's symmetric key through StateService into chrome.storage.local. On logout, it's inaccessible until you decrypt with your master password, just like vault data. Never plaintext on disk.
Implementation would follow existing patterns: add a field to the Account model, extend StateService with get/set methods for the encrypted data, create a service in the vault library for encryption/decryption and LRU logic, and integrate the autocomplete UI into the cipher form using existing design components.
I'm happy to implement this with full encryption, tests, and documentation if it aligns with Bitwarden's direction.
Does this resonate with anyone? Am I the only one annoyed by this? Open to feedback and concerns I haven’t considered.
Beta Was this translation helpful? Give feedback.
All reactions