Huh- interesting topic and use case! Google Chrome’s autofill has definitely played a pivotal role in my day-to-day online shopping, but I haven’t really seen any mention of coopting that in an Axure prototype. Overall, the functionality of autofill detection is unique to each individual browser. From my web search, it looks like Google Chrome looks for a range of components parts including the specific name IDs for widgets and the total number of successive input fields. Here are a couple relevant articles:
After testing this more in your file, it’s also looking like the z-index of each named label and corresponding input field would also matter. So, organizing them more linearly in the Widget Manager Pane (of RP 7) can help–here’s a screenshot:
Here’s an edited version of your v7 file as well (which seems to work so long as there’s data saved in Chrome Autofill to begin with):
Check Out Form_Edit.rp (177 KB)
Does that file and setup work on your end? It does appear possible to tweak the project setup and get Chrome to detect the fields of an Axure prototype. To get this done more precisely, however, may require more programmatic intervention outside of the native setup of an Axure RP project. I hope this is helpful, though!
ChromeAutofillSample.rp (50.3 KB)