New issue
Advanced search Search tips

Issue 716020 link

Starred by 2 users
Status: Fixed
Owner:
anthonyvd@chromium.org
Closed: Jul 2017
Cc:
rouslan@chromium.org
anthonyvd@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , All
Pri: 3
Type: Bug



Sign in to add a comment

[Payments] Handle FullCardRequest errors with more granularity

Project Member Reported by ma...@chromium.org, Apr 27 2017 
Right now, closing the prompt or a network error both call ResultDelegate::OnFullCardRequestFailed, which is not granular enough for the Payment Request UI because one is user-initiated and the other one not.

Comment 1 by rouslan@chromium.org, Apr 27 2017 

What should happen in user vs non-user initiated error cases?

Comment 2 by ma...@chromium.org, Apr 27 2017 

If user initiated (say they close the prompt), no error needs to be shown. For non-user initiated (i.e. network or unmask error), there should be an indication of what happened. We have the detailed error codes, we just need to use them. This bug tracks that.

Comment 3 by ma...@chromium.org, Jun 5 2017

Owner: anthonyvd@chromium.org
Status: Assigned (was: Available)
I think this may have been tackled by Anthony

Comment 4 by lafo...@chromium.org, Jun 27 2017

Components: -UI>Browser>Autofill>Payments UI>Browser>Payments

Comment 5 by anthonyvd@chromium.org, Jul 24 2017

Status: Fixed (was: Assigned)
Yeah, this was fixed way back in r472887
►

Sign in to add a comment