See https://www.chromium.org/Home/chromium-security/security-faq#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model- for a discussion about why this isn't a security issue.

There may or may not be a small functional issue here, however.  The purpose of a verification it to make sure you typed the intended password correctly, given that it is masked to prevent 'shoulder-surfing'.  Having chrome autocomplete the field might be an issue, since any typos would be passed through as-is.

However, given that the chrome password manager knows the correct value, we might not care, and this makes things easier in that case.  Re-assigning as a functional issue.

Thanks for the report and for the comment in #1, which I agree with.

Filling the password is important for the main use-case: transferring the burden of remembering the password from the user to Chrome. Retyping stuff for verification is meant for humans and it is pointless for computers taking care of the data. But that's the issue of the page, not Chrome.