GitLab

Before this patch, calling PaymentRequest.canMakePayment() after its
value has been calculated would return "false", ignoring the fact that
secure payment confirmation is being requested, for which
canMakePayment() should return "true" if an authenticator device is
available, even if there are no credentials on file.

This patch changes PaymentRequestState::CanMakePayment() to use
GetCanMakePaymentValue() after all apps have finished queried. This
method takes into account whether secure payment confirmation is being
requested and an authenticator is available.

After this patch, PaymentRequestState.canMakePayment() always returns
"true" for secure payment confirmation when an authenticator is
available (if the secure payment confirmation feature is enabled).

Bug: 1123148
Change-Id: I4bb4895cbc1c7db1d84a19c9d753d5766769ad84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383693Reviewed-by: Nick Burris <nburris@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#802927}