diff options
author | sebsg <sebsg@chromium.org> | 2016-03-01 12:45:03 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2016-03-01 20:47:05 +0000 |
commit | 0a8abd1cd85e42b969740ca38e01df01ff244743 (patch) | |
tree | 398fa1c65f348080b5286962c428a3dc4c4a4fee /device/bluetooth/bluetooth_remote_gatt_descriptor_win.cc | |
parent | c9812c390c829563bfdb5ec7b0effd06f21a1246 (diff) | |
download | chromium_src-0a8abd1cd85e42b969740ca38e01df01ff244743.zip chromium_src-0a8abd1cd85e42b969740ca38e01df01ff244743.tar.gz chromium_src-0a8abd1cd85e42b969740ca38e01df01ff244743.tar.bz2 |
Added two new field types : CREDIT_CARD_NAME_FIRST and CREDIT_CARD_NAME_LAST. Modified the heuristics to recognize these two new fields. Added code to be able to fill these new fields with the data already available.
This will fix Keurig.com and sites like this example:
https://f117f41fdbc2c18ce6861c4fac2e807ecf7f1d75.googledrive.com/host/0B3xzZ-vFr2LRU0FlVEhGa09uSDA
Since it's still pretty conservative. It won't fix sites like Cabelas.com where the fields are named "firstname" and "lastname"
The original heuristics predictions on Keurig.com were:
NAME_FIRST | card_firstNameOnCard | First Name*
NAME_LAST | card_lastNameOnCard | Last Name*
UNKNOWN_TYPE | card_accountNumber | Card Number*
UNKNOWN_TYPE | card_cardType | Card Type
UNKNOWN_TYPE | | Please select a card type
UNKNOWN_TYPE | card_expirationMonth | Expiration Date*
UNKNOWN_TYPE | | Month
CREDIT_CARD_EXP_MONTH | card_expirationYear | Expiration Date*
CREDIT_CARD_EXP_4_DIGIT_YEAR | | Year |
CREDIT_CARD_VERIFICATION_CODE | card_cvNumber | Security Code*
TBR=thestig@chromium.org
BUG=579174
TEST=AutofillManagerTest, FormStructureTest
Review URL: https://codereview.chromium.org/1694443004
Cr-Commit-Position: refs/heads/master@{#378551}
Diffstat (limited to 'device/bluetooth/bluetooth_remote_gatt_descriptor_win.cc')
0 files changed, 0 insertions, 0 deletions