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

Issue 619326 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature

Blocking:
issue 603635


Participants' hotlists:
Payment-Conversion

Show other hotlists

Other hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Chrome should store frecency information for payment apps.

Project Member Reported by rouslan@chromium.org, Jun 11 2016

Issue description

Every time the user selects Android Pay (for example) in PaymentRequest, Chrome should increment the count and update the last use time of using that particular payment app.

This information should be stored in a new autofill table.

This information should be synchronized, which requires a new sync protobuf and sync controller.

Frecency algorithm for PaymentRequest payments should include both credit cards and payment apps on equal footing.

Also need to use website's ordering of payment methods as a signal in the sorting algorithm.
 

Comment 1 by plaree@chromium.org, Jun 13 2016

Cc: plaree@chromium.org jnaveen@chromium.org

Comment 2 by gangwu@chromium.org, Jun 22 2016

Labels: Sync-Triaged
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 5 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -M-54 -MovedFrom-53
Components: -UI>Browser>Autofill>Payments UI>Browser>Payments

Comment 6 by treib@chromium.org, Jan 29 2018

Labels: -Pri-1 Pri-2

Comment 7 by pav...@chromium.org, Jan 29 2018

Labels: SyncHandoff2018

Comment 8 by ma...@chromium.org, May 1 2018

Status: Untriaged (was: Available)
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment