Username and Email as separate fields
I have the same problem with Bitwarden. This is the only thing that would keep me from switching from Enpass. I don't want to have to create a custom field each time, and I'm sure many proton users have multiple emails to keep track of.
The way that Enpass does it is ideal IMO. When creating a login there’s separate fields for email, username, password, URL, phone number, security question/answer, tags, notes. Even though most of these will be unnecessary most of the time, they’re available in the creation menu, so you don’t have to add a new field each time. Obviously, once you create and save the login, it’ll only display the info you’ve filled in until you want to make edits.
Enpass’s approach is having all the most common fields available at the start when creating a login, and then allowing the user to just fill in what they need without having to create custom fields for things that are relatively common.
This is the most convenient and least frustrating way to do it. It would make a world of difference for me, and I’m sure many other users.
Jon Grose commented
Adding an alias is very easy, I love it, but I cannot then add a username without removing the alias which interferes with the SimpleLogin integration.
When adding an alias, it automatically replaces the username field and then autofills any username field with your alias. So literally any time a website actually uses a username (which is a lot), you have to fill it manually.
This is a giant problem and I don't understand how this made it past day 1 of development...
If you add an alias to a login, it automatically replaces and autofills the username field. This is a giant hassle when logging into any website that *actually uses a username* because it will autofill your email instead and then you'll have to manually erase it and re-populate with your username.
How this ever get past day 1 of development is mind-boggling.
Mike Gaudiello commented
this is a huge inconvenience
Christophe Dervieux commented
As a Dashlane user I also find this field missing.
I can be easily done with Manual creation, but this is especially missing with automatic login creation when you create an account on a website.
The proton passe extension will detect new creation, and suggest to add a login. but it will save only the username and not the associated email. When using an alias, it would be nice to also have this field automatically created
Michael Allen commented
It would if P. Pass would recognize that field as a Username. Enpass user as well and Im so glad Proton made this, but its missing TONS of niceties from Enpass that is already hard-stopping my migration (No Enpass Migration feature being one of them.) That being said I can do the hand-jam, but stuff like this is nearly essential.
Couldn't this be accomplished by adding a text field and naming it email and then adding your email address when you want/need it separate from the username/email field?