Chrome-side implementation of AutocompleteErrorEvent#reason.

chrome/browser/autofill/autofill_manager.h

Index: chrome/browser/autofill/autofill_manager.h
diff --git a/chrome/browser/autofill/autofill_manager.h b/chrome/browser/autofill/autofill_manager.h
index 8318480bb84831b5b06d4a4556ca38c33c314fc9..64b01f49257bd9c592da8c2a98cc752ad487c001 100644
--- a/chrome/browser/autofill/autofill_manager.h
+++ b/chrome/browser/autofill/autofill_manager.h
@@ -28,6 +28,7 @@
 #include "chrome/browser/autofill/personal_data_manager.h"
 #include "content/public/browser/web_contents_observer.h"
 #include "content/public/common/ssl_status.h"
+#include "third_party/WebKit/Source/WebKit/chromium/public/WebFormElement.h"
 
 class AutofillExternalDelegate;
 class AutofillField;
@@ -170,9 +171,10 @@ class AutofillManager : public content::WebContentsObserver,
   bool OnFormSubmitted(const FormData& form,
                        const base::TimeTicks& timestamp);
 
-  // Tell the renderer the current interactive autocomplete failed somehow.
-  // Exposed for testing.
-  virtual void ReturnAutocompleteError();
+  // Tell the renderer the current interactive autocomplete finished.
+  virtual void ReturnAutocompleteResult(
+      WebKit::WebFormElement::AutocompleteResult result,
+      const FormData& form_data);

[Ilya Sherman, 2013/01/09 08:54:39]

Hmm, why not pass an error with a reason, or a success with form data?  Is it
possible to have multiple types of success?

[Dan Beam, 2013/01/09 18:37:38]

Because I didn't like that I ended up with am error method which checked if the
result is a success (seemed odd). This also saves a bit of redundant code.

 
  private:
   // content::WebContentsObserver: