Version 67

When changing or generating a new password, the generated password may be saved as a separate credential without a username. The username is expected to be saved the next time the user logs in.

However, we offer no typing-free way to use two different parts of the credentials, so that they can be combined into the changed credential. The user has to fill their nameless password and then type their username.

Example:
1. Reset your github.com password by generating a new password.
2. Visit the login page. Your old credentials should be autofilled.
3. On the password field, select the new credential. The password is replaced and the username is cleared.
4. You now have to manually type the old username to login (and if you accept the filling suggestion, the filled password will be replaced with the outdated password again)

One solution could be to not fill an empty username (i.e. not clear the username to replace it with an empty string). 
The flow now becomes: 
1. The old credential is filled
2. The user selects the nameless password on the password field. The nameless password is filled and the old username is kept.
3. The user can now log in.