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

Issue 864428 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Aug 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Move Payments Customer ID out of priority prefs and into AutofillWalletSpecifics

Project Member Reported by feuunk@chromium.org, Jul 17

Issue description

In order to remove the dependency from Wallet on having the priority pref data type on, we want to move the payments customer ID from priority prefs into AutofillWalletSpecifics.

For those with access, see design here: https://docs.google.com/document/d/1Miacsn0pX-Mj-a7YYha6fCCBZ9115Gncwt4H1Il4THY/edit
 
Status: Available (was: Untriaged)
Cc: jiahuiguo@google.com jsaul@google.com dlkumar@google.com
Project Member

Comment 3 by bugdroid1@chromium.org, Jul 17

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c639169e64bae6f735544a3f7abb1a48629ad1bc

commit c639169e64bae6f735544a3f7abb1a48629ad1bc
Author: Florian Uunk <feuunk@chromium.org>
Date: Tue Jul 17 16:53:37 2018

Properly handle unknown WalletInfoType values.

The previous DCHECK meant that we can't introduce a new type in the
future without breaking old clients. Instead, just ignore types we
don't know about.

Bug:  864428 
Change-Id: Iaa31e2b0e6d501e14fcc1fa840110fc22f5c100a
Reviewed-on: https://chromium-review.googlesource.com/1140058
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Florian Uunk <feuunk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575680}
[modify] https://crrev.com/c639169e64bae6f735544a3f7abb1a48629ad1bc/components/autofill/core/browser/webdata/autofill_wallet_syncable_service.cc

Mergedinto: 870936
Status: Duplicate (was: Available)

Sign in to add a comment