Sorry to tell you, but the process of saving passwords is wrong!
When Proton Pass propose a new generated Password thats great!
But how can Proton Pass be sure that the new password was:
1. Acceped by the Target Webpage? (Rules of Password lenght, Complexity...
2. Is the new password realy safed on the target website? Some tests maybe...
3. What about the "final" save in Proton Pass. Can i chose where i want save this new password, what when i do a mistake and the new generated password is lost. -> Not every pressious Account have a reset. So the consequence is, that you block the account with a new generated password that you don't know and you cant reset. This account is "******" you loose it. I loose 2 of my accounts this way, so Proton pass is a account "killer".
4. The generated password history it's not working. So you can't even try to use the list of generated passwords.

So the correct way:
Safe only passwords in Proton Pass when you are sure that the new password is saved in the target:

1.. Generate password
2.. Save new password temporary
3. Log with new password to the target
4. When ok, save password with the user and new generated password in Proton Pass.

The actual process of proton is weak, unfriendy und have many risk of loss your access to the target.