Chrome Version: 69.0.3466.0
URL: https://accounts.google.com

After the user entered their username, accounts.google.com updates the form to show the password field and sticks the username into <input type="email" name="identifier" ... autocomplete="off" id="hiddenEmail">, with the value being the username.

accounts.google.com also annotates the password field with autocomplete="current-password".

The autofill server sends a vote that the "identifier" field is actually a username, but comments on no password fields.

As a result, when the new parser tries server hints, it throws them away for having no password field included. Then it goes on to the autocomplete analysis, and finds the password, but not the username.


There are no consequences on accounts.google.com, however:
(1) Saving works correctly, thanks to looking for non-empty fields.
(2) Filling works correctly, because as long as the username field is editable (in the first phase), it is marked up correctly as autocomplete="username", so it gets filled.