Status of Chrome implementation of requestAutocomplete as of 5/15/13.

[Albert Bodenhamer]

Summary:

The feature is still locked behind the --enable-interactive-autocomplete flag in Dev and Canary channels.  We plan to enable by default this week.

Channels:

Dev & Canary (behind a flag)

Platforms:

Windows & Chrome OS

Errata:

• Need to either pass “--enable-interactive-autocomplete” on the command line or choose “enable” for the “Interactive autocomplete” experiment in chrome://flags

• All Wallet interactions are still pointed at a test server by default.  Any attempt to charge card numbers generated by Wallet test servers will fail.

• UI still needs a lot of polish.  For example, “Loading” states and smooth transitions are missing.

• We have occasionally seen users get into a state where clicking submit will simply gray out the submit button, but leave the dialog running.  There are a number of scenarios that will end in this state, but they all result from attempting to use an instrument/address that Wallet has problems with.

Workaround: Visit https://wallet-web.sandbox.google.com/manage/paymentMethods and review all payment methods, addresses, and phone numbers.  You should have at least 1 instrument and 1 address and both should be complete.  Alternatively, choose “Pay without Google Wallet”.

• Full list of known issues: https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DUI-Browser-Autofill-Interactive

--
Albert Bodenhamer | Software Engineer | abodenha@chromium.org 

[abod...@chromium.org]

As of today, requestAutocomplete is enabled by default in Canary on Windows.  The change should propagate to Dev channel with the next push.

The feature can be disabled in chrome://flags by setting "Enable interactive autocomplete" to "disabled".

A new known issue is http://crbug.com/226735  On Windows, backspace will sometimes close the window.  We're investigating and hope to have a fix soon.

If you see issues please file bugs at http://crbug.com or email this list.

Thanks.