Forum Discussion
Passwords that don't save in time
Having encountered the problem of unsaved password quite a few times, I've made the habit of revealing and copying the password into the primary paste buffer. That way I can add it to the item and paste it into the password field if needed - a process which may prompt a save.
Memory claims that Watchtower might privilege autogenerated passwords, but not pasted passwords which were autogenerated, however that is not a reliable source of truth.
Password setting workflows which fall far from best practices and don't revel that they can't handle a long password, or don't allow "special" characters because they get passed through to the back end unhashed and will break the database, or are trying to run some JavaScript validation process which only works when typing, or... can result in multiple "old" invalid passwords cluttering the item history as the form is refilled and the new (worse) password is saved. It would be nice to be able to purge these.