Browser autofill: fill the login matching the username already typed (keyboard shortcut) #22005
Nxtmaster10
started this conversation in
Password Manager
Replies: 1 comment
|
✨ 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! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
✅ Code Contribution Proposal
Code Contribution Proposal
I'd like to add an option to the browser extension that makes the autofill keyboard shortcut (Ctrl+Shift+L) fill the login matching the username you have already typed, instead of always starting from the first / last-used entry. Happy to build it myself if the team is open to it.
This builds on #377 (repeat shortcut presses cycle through logins). One of the comments there suggested pretty much this - check what is already in the field and pick the account that matches. On sites where I have a few accounts, the shortcut fills one of them and I have to keep pressing to get to the right one. If I have already typed part of my username, the extension could just pick the correct login the first time.
Proposed behaviour
Scope and safety
It only reads the field on a genuine top-frame shortcut press, so a subframe can never influence which login is chosen. It never touches password fields (text / email / tel only), the read value is length-capped, and the automated auto-submit-login flow is left out. The whole thing is opt-in and off by default.
Status
I have this working locally with unit tests and can open the PR once the approach is agreed. I am also fine putting it behind a feature flag if that is preferred.
Screenshot
Related
All reactions