CWVCreditCardVerifier needs Risk Data to perform verification |
||
Issue descriptionCWVCreditCardVerifier needs to contact payments API underneath and requires additional risk data that can only be provided by 1st party client apps.
,
Oct 25
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8960154b5498a7ab27cddc9b56ba8909b2050cb9 commit 8960154b5498a7ab27cddc9b56ba8909b2050cb9 Author: John Z Wu <jzw@chromium.org> Date: Thu Oct 25 04:33:13 2018 Fix timing for getting risk data in CWVCreditCardVerifier. CWVCreditCardVerifier should ask for risk data when user begins verification because that's when |_dataSource| will be available. Bug: 895694 Change-Id: Ic74b638eff9ed473767132722e48da36616c76af Reviewed-on: https://chromium-review.googlesource.com/c/1298113 Commit-Queue: John Wu <jzw@chromium.org> Reviewed-by: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#602611} [modify] https://crrev.com/8960154b5498a7ab27cddc9b56ba8909b2050cb9/ios/web_view/internal/autofill/cwv_credit_card_verifier.mm [modify] https://crrev.com/8960154b5498a7ab27cddc9b56ba8909b2050cb9/ios/web_view/internal/autofill/cwv_credit_card_verifier_unittest.mm [modify] https://crrev.com/8960154b5498a7ab27cddc9b56ba8909b2050cb9/ios/web_view/public/cwv_credit_card_verifier.h
,
Dec 4
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Oct 16