Make 1Password automatically ask to save password after login is done

@Joy_1P I'm sorry to disagree, but saving an entry before its data is actually applied on the website is conceptually wrong. All this is a synchronization problem between 2 database tables: one on the website and one in 1Password. The concept of a database is to have valid data all the time, never store invalid data. So if there must be 2 independent updates that have to be applied either both or none at all, there has to be a transaction opened that can roll back the incomplete parts if necessary, and there has to be a commit operation that finalizes the transaction.
The website cannot trigger the commit, because it doesn't know about the other party. So 1Password has to keep entered credential data, then commit. And a commit can only take place, if both operations were done successfully. This can only be after the website accepted the (new) password, never before.
If it can happen that a password submission isn't successful, so 1Password cannot detect if the website accepted the password, the problem is on the website part. In this case, the transaction is still pending and 1Password has to still keep the entered credential data and ask the user the next possible moment (when the user starts to navigate on the website) if the data should be commited to some entry or thrown away.
As far as I remember, the Chrome password manager for example keeps this temporary data in a notification as long as the user doesn't decide to save or refuse saving.