Unable to reproduce the issue on Mac-10.12.2 and Windows-7 using chrome version 56.0.2924.87 and canary 58.0.3007.0 with the steps mentioned above.

Observed that Chrome has auto filled the username and password fields correctly.
could you please upgrade the chrome to latest version and try in clean profile without any apps and Extensions and please let us know your observations if the issue still persists.

Thanks..

Can you provide a link to an example page on the web that is exhibiting the problem?

Unfortunately I experience this on a product I'm developing which is not yet live and available to the public. I can reproduce it on a clean, up to date version of Canary (58.0.3019.0).

I appreciate this isn't much help at this moment in time. Perhaps it would be best to re-open this in about a month when the product will be launched.

Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

vabr, can you take a look?

I suggest trying autocomplete="username email" for the desired username field.

Other than that, the current heuristics Chrome uses is indeed to take the first text field before the password field.

We are also just adding some more interesting heuristics, but they are hosted on a support server and might only trigger for sufficiently frequently visited public sites, IIUC. I'm adding dvadym@ and kolos@ to correct me if I'm wrong.

Also, dvadym@ and kolos@ feel free to either keep this open as a reminder, or close if the effort fixing this is already tracked elsewhere. Thanks!

Here more details, on our recommendation on password form structure
https://www.chromium.org/developers/design-documents/form-styles-that-chromium-understands

You can also add autocomplete="new-password" for a password field on the registration form, it will prevent from filling this field.

Adding "username" to the autocomplete for the email field does the trick, thanks very much all.

Note - I used this page to know what to use on each field: https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill

This has no mention of the "username" value, so it might be worth getting whichever team has control over this to add it.

Thanks for pointing out that the page with the autofill advice does not mention the passwords-related fields. The advice for passwords is summarised on https://www.chromium.org/developers/design-documents/form-styles-that-chromium-understands. I posted a comment on the page you linked to point people there, and I will check if we can get a post-publishing edit to that autofill article.

Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]