3 years, 11 months ago
(2017-01-20 23:25:53 UTC)
#1
Patchset #1 (id:1) has been deleted
gogerald1
Description was changed from ========== format format surface settings UIs to allow users enable and ...
3 years, 11 months ago
(2017-01-20 23:26:25 UTC)
#2
Description was changed from
==========
format
format
surface settings UIs to allow users enable and disable Android payment apps in
payment request
Redesign Autofill settings UIs
BUG=679743
patch from issue 2636023002 at patchset 140001
(http://crrev.com/2636023002#ps140001)
==========
to
==========
Surface settings UIs to allow users enable and disable Android payment apps in
payment request
BUG=679743
patch from issue 2636023002 at patchset 140001
(http://crrev.com/2636023002#ps140001)
==========
gogerald1
The CQ bit was checked by gogerald@chromium.org to run a CQ dry run
3 years, 11 months ago
(2017-01-20 23:27:55 UTC)
#3
Dry run: Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds/139853) ios-simulator on ...
3 years, 11 months ago
(2017-01-21 00:40:42 UTC)
#9
3 years, 11 months ago
(2017-01-24 16:30:51 UTC)
#10
Patchset #1 (id:40001) has been deleted
gogerald1
Patchset #1 (id:60001) has been deleted
3 years, 11 months ago
(2017-01-24 16:30:57 UTC)
#11
Patchset #1 (id:60001) has been deleted
gogerald1
Patchset #1 (id:80001) has been deleted
3 years, 11 months ago
(2017-01-24 16:43:05 UTC)
#12
Patchset #1 (id:80001) has been deleted
gogerald1
Description was changed from ========== Surface settings UIs to allow users enable and disable Android ...
3 years, 11 months ago
(2017-01-24 16:45:08 UTC)
#13
Description was changed from
==========
Surface settings UIs to allow users enable and disable Android payment apps in
payment request
BUG=679743
patch from issue 2636023002 at patchset 140001
(http://crrev.com/2636023002#ps140001)
==========
to
==========
Surface settings UIs to allow users enable and disable Android payment apps in
payment request
The feature is disabled by default. It can be enabled via a flag:
chrome://flags/#android-payment-apps
To test the new functionality:
1) Install BobPayWithIsReadyPayService.apk:
https://drive.google.com/a/google.com/file/d/0B3ISiXgGE1MNSnFXcnkwQ1FSbGc/vie...
2) Enable chrome://flags/#android-payment-apps.
3) Go to setttings/Autofill and payments/Payment apps
BUG=679743
patch from issue 2636023002 at patchset 140001
(http://crrev.com/2636023002#ps140001)
==========
3 years, 11 months ago
(2017-01-24 19:34:58 UTC)
#22
Dry run: This issue passed the CQ dry run.
Ted C
lgtm w/ small comments https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java File chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java (right): https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java#newcode10 chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java:10: public class PaymentPreferences { I ...
3 years, 11 months ago
(2017-01-25 19:05:43 UTC)
#23
https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java File chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java (right): https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java#newcode10 chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java:10: public class PaymentPreferences { On 2017/01/25 19:05:43, Ted C ...
3 years, 11 months ago
(2017-01-25 19:43:20 UTC)
#24
https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/sr...
File
chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java
(right):
https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/sr...
chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentPreferences.java:10:
public class PaymentPreferences {
On 2017/01/25 19:05:43, Ted C wrote:
> I might call this PaymentPreferencesUtil to make it clear that it isn't a
> Preference itself.
Done.
https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/sr...
File
chrome/android/java/src/org/chromium/chrome/browser/preferences/autofill/AndroidPaymentAppsFragment.java
(right):
https://codereview.chromium.org/2647573005/diff/140001/chrome/android/java/sr...
chrome/android/java/src/org/chromium/chrome/browser/preferences/autofill/AndroidPaymentAppsFragment.java:45:
for (Map.Entry<String, Pair<String, Drawable>> app : appsInfo.entrySet()) {
On 2017/01/25 19:05:43, Ted C wrote:
> do we want this to be predictably ordered? Should we order by name?
>
> Wondering if a Map is actually the best here. Should we use a List of
> PaymentAppInfo objects that is ordered by something?
That's a good idea. Sorting by name also sounds good to me. Will do it in a
separate CL. I am working on sorting payment apps and instruments in payment
request as well.
gogerald1
The CQ bit was checked by gogerald@chromium.org
3 years, 11 months ago
(2017-01-25 19:43:26 UTC)
#25
Issue 2647573005: [Payments] Allow users enable and disable Android payment apps in payment request
(Closed)
Created 3 years, 11 months ago by gogerald1
Modified 3 years, 11 months ago
Reviewers: please use gerrit instead, Ted C
Base URL:
Comments: 16