UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36

Steps to reproduce the problem:
1. Create a form with name and address inputs
2. Use the Places API on a form for address autocomplete
3. Navigate to the form and enter your name in the name field
4. Choose an Autofill suggestion
5. Observe that the address field is not filled by the selection

What is the expected behavior?
Disabling a field as an Autofill trigger should not preclude that field being completed by a selected Autofill option. A separate option should exist that would allow an input to be used as a trigger for the Places API (and not Autofill) that still allows the user to complete the form with Autofill from a different input.

For example, a form with name and address fields might allow Autofill on the first and last name fields, but use the Places API on the address field to improve the quality of address data. As a compromise for user convenience we would like the Autofill to continue to fill in this information. The only way to do this at present is to remove the autocomplete attribute added by the Places API, however this results in the poor UI experience described in https://bugs.chromium.org/p/chromium/issues/detail?id=473851 

What went wrong?
Developers are faced with a choice of Autofill not completing all fields, not using the Places API, or having a very poor user experience.

Did this work before? N/A 

Chrome version: 52.0.2743.82  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

Related to https://bugs.chromium.org/p/chromium/issues/detail?id=473851