https://www.abercrombie.com has two forms: sign-in and sign-up. Both have one visible text field, one visible password field (called 'logonPassword', same name in both forms) and one invisible password field (called 'logonPasswordRemembered').

When Chrome loads https://www.abercrombie.com, the autofill server indicates that 'logonPasswordRemembered' is the name of the new password field, and there is no current password field.

The new parser (--enable-features=new-password-form-parsing) believes the server, while the old one thought that 'logonPasswordRemembered' is the current password field and 'logonPassword' the new password field.

This could affect saving, although likely either the visible field will be distinguished by having a value, or the hidden field will have a copy of that value.

Once we implement using the new parser for saving, we need to check how it behaves here and fix as needed.