Autofill: Set requirements for number of recognized fields in an autofillable form

components/autofill/core/browser/phone_field.cc

Index: components/autofill/core/browser/phone_field.cc
diff --git a/components/autofill/core/browser/phone_field.cc b/components/autofill/core/browser/phone_field.cc
index d7860497378a55090a40234e907f1c4e39ef0f5a..0f9ff5b0f851ff925094b4fe1bfe9f12a22037af 100644
--- a/components/autofill/core/browser/phone_field.cc
+++ b/components/autofill/core/browser/phone_field.cc
@@ -240,6 +240,16 @@ bool PhoneField::ClassifyField(ServerFieldTypeMap* map) const {
   return ok;
 }
 
+size_t PhoneField::FieldCount() const {

[Evan Stade, 2015/01/21 22:52:50]

why not just return 1? Why should three separate inputs [   ] [   ] [    ] count
differently from one big one [          ]?

[Lei Zhang, 2015/01/22 08:07:37]

Recognizing many fields in a phone number is a stronger signal than just one
field that's a PHONE_HOME_WHOLE_NUMBER, which could be the type of badly
classified fields we are trying to address in this CL.

+  size_t count = 0;
+  for (size_t i = 0; i < FIELD_MAX; ++i) {
+    if (parsed_phone_fields_[i])
+      ++count;
+  }
+
+  return count;
+}
+
 PhoneField::PhoneField() {
   memset(parsed_phone_fields_, 0, sizeof(parsed_phone_fields_));
 }