I stated that the value on the password field is not set after user interactions in a new window. This is true but I just noted another inconsistency:
* The value is not set after user interaction when after re-loading the page with the refresh button.
* The value is set as expected if you press F5 to reload the page.

Unable to reproduce the issue on the reported chrome version stable 61.0.3163.100 and on the latest canary 63.0.3239.9 using Ubuntu 14.04

Could you please re-try the scenario by creating a new profile 

Please follow below steps to create a New profile
(i). Launch chrome>>go to Settings)
(ii).Under the section headed People, Click on link Manage other people>>Add person

I re-tested this issue on Ubuntu 16.04 and Windows 10 with Chrome 61.0.3163.100. 
I created new profiles/persons and was able to reproduce it.

Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Just found out what triggers this bug: We were setting the value of the password field to an empty string which seems to be noticed by the autocompletion.

The autocompletion obviously refuses to fill a textfield when a value has been set before. This behaviour has been changed and couldn't be observed in chromium 57.

Unable to reproduce the issue on Ubuntu 14.04 using chrome reported version-61.0.3163.100,stable-62.0.3202.75 & dev-63.0.3239.18 as per C#0.

User able to login successfully with autofilled credentials.

Please find the attached screen cast for reference .Could you please check this issue on latest chrome versions & let us know your observations on the same.

Thanks..!

Deleted: 775417.mp4 3.1 MB

	775417.mp4 3.1 MB View Download

You did reproduce the problem. The dialog "you have been hit by a bug of the autofill feature of your browser" is only displayed if the value of the text field is not set by the autofill feature.

This is what currently happens:
1. The page is loaded
2. We set the value of the password field to an empty string ("")
3. The chrome autofill feature displays the placeholders on the password field.
4. When you click on login, the autofill feature detects that the value of the password field has been set from JS already and does not set the value again.

The autofill feature has overridden the value of the field in version 57, no matter if the value has been set from JS or not.

The workaround we implemented (not released yet) was to not set the value of the password field. However, it took some time to find out that chrome does not override the value anymore...

Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce the issue on the reported chrome version stable 61.0.3163.100 and on the latest canary 64.0.3254.0. using Ubuntu 14.04 with the steps mentioned in comment#0. Attaching the screen cast of the same. As the reporter is facing the issue even in new profile, could some one from the respective team have a look into this. 

Deleted: 775417.ogv 2.0 MB

	775417.ogv 2.0 MB View Download

The screencast shows that you have stored the password within the app. 

You will not be able to reproduce this issue under this circumstandes, as you did not use the password manager of the browser.

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!