Unable to reproduce the issue on Win-10 using chrome reported version #61.0.3163.79 and latest canary #63.0.3213.3.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to: https://codepen.io/anon/pen/yomBZr/
2. filld the form
3. saved username and password
4. Navigated to: https://codepen.io/anon/pen/vJoBwJ/
5. clicked on 1st password field
6. Used Password for previously saved one.
7. Observed that chrome filled the hidden username field with autocomplete="username" parameter as expected.

peter@ - Could you please verify the screen cast and please let us know if anything missed from our side. If possible please provide a screen cast explaining the exact issue.

Thanks...!!

Deleted: 763534.mp4 1.0 MB

	763534.mp4 1.0 MB View Download

In the video you can see chrome filled the search field with autocomplete="off"
and ignored the hidden field with autocomplete="username" you reproduced the issue.

Deleted: Capture.PNG 109 KB

	Capture.PNG 109 KB View Download

Thank you for providing more feedback. Adding requester "krajshree@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

When you click on submit btn on 2nd page, you will see it is ignored the username field and put username into search field, if you remove search fields from the test  chrome put username into the hidden username field (how it should in all circumstances) If you need more detailed test, feel free to ask me.

Tested on reported Chrome #60.0.3112.90, latest stable #61.0.3163.91, Canary #63.0.3219.0 on Windows 10, Mac 10.12.6, Ubuntu 14.04 and able to reproduce the issue. 

This is a non-regression issue and able to reproduce from M-50 #50.0.2624.0. Marking it as untriaged so that issue gets addressed.

Attached screenshot for reference.

Thanks.

Deleted: 763534.PNG 115 KB

	763534.PNG 115 KB View Download

Thanks for the report.

Indeed, looking at FindUsernameElementPrecedingPasswordElement in components/autofill/content/renderer/password_autofill_agent.cc, currently Chrome fails to take hidden autocomplete="username" fields into account when looking for fields to fill.

Vadym, what do you think of visibility overriding the autocomplete attribute, is that expected? If there is no text field at all, Chrome will happily fill just the password (which is the most important information to fill). So I would say. Chrome could accept the wish not to fill the username if it's expressed through autocomplete attributes (perhaps even by respecting the autocomplete=off on the visible field?)

Also, do you know why the current-password is not filled on load? Is that because Chrome only does it when the username field is also present and visible?

Please consider my opinion: as a developer when I create the fields, I create them on purpose. If there is a hidden fields before password it can be anything, but when I add autocomplete="username" to the field I want to tell the browser that is the username field. It can be hidden or I can play with css to hide it etc... But it is not "accidentally" has autocomplete attribute.

So my point of view autocomplete should override the visibility.

And one more thing:
If there is no other visible field in the form, Chrome find the hidden autocomplete="username" field and fill it with the username. Based on this behavior I think it should act the same way when other fields are in the form.

pe...@ In principle I agree with your arguments in comment 10. We need to discuss it in a team. For now you can move a search field outside <form> tag.

dvadym@ I can't. It is ASP.NET Web Forms, everything in one big form. I know it is a bad practice, but that technology out there for 7 years.