New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 802142 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 871791
Owner:
Last visit > 30 days ago
Closed: Oct 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

`canMakeyPayment` limitation is too tight

Project Member Reported by agektmr@chromium.org, Jan 16 2018

Issue description

Chrome Version: Version 65.0.3319.0 (Official Build) canary (64-bit)

Consecutive call of `canMakePayment()` is restricted and second call always returns exception.

What steps will reproduce the problem?
(1) Go to https://output.jsbin.com/savated
(2) Press "Start"

Find the code here: http://jsbin.com/savated/edit?html,js

What is the expected result?
To see "available" or "not available" on both "Credit" and "Prepaid".

What happens instead?
"Prepaid" always "exception"

I'm expecting cases where a developer wants to use multiple different set of payment request instances to enable different set of branded buttons. In order to determine if showing those branded buttons, calling `canMakeyPayment` would be the best practice, but this limitation prevents to do it.

I'd like this restriction to be relaxed.
 
Components: Blink>Payments
Owner: durgapandey@chromium.org
Durga, please help triage.
Status: Assigned (was: Untriaged)
Mergedinto: 871791
Status: Duplicate (was: Assigned)
Going to relax the quota to per-method level restrictions, but iteration within the wallet is still not allowed. So two separate queries for prepaid and credit card is not allowed, but multiple queries for autofill cards and payment apps is allowed. Going to continue this work in issue 871791.

Sign in to add a comment