PaymentHandler: Implement GetAllPaymentApps().

components/payments/mojom/payment_app.mojom

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 module payments.mojom;
 
 import "components/payments/mojom/payment_request.mojom";
 import "mojo/common/time.mojom";
 import "url/mojo/url.mojom";
 
@@ skipping 19 matching lines @@
 
 enum PaymentHandlerStatus {
   SUCCESS,
   NOT_IMPLEMENTED,
   NOT_FOUND,
   NO_ACTIVE_WORKER,
   STORAGE_OPERATION_FAILED,
 };
 
 struct PaymentInstrument {
+  int64 registration_id;

[Tom Sepez, 2017/05/09 17:07:21]

Where does this ID come from?  Is unique to a renderer?  Is it guessable?  If
some other renderer guesses this ID, what's the worst that can happen?

[zino, 2017/05/09 17:16:57]

These three members are only used in browser side.
Is this usage restricted? (if do not allow this way, we will write a new
additional class?)
If not so, I leave a comment here like that:
"These three members are only used in browser side.. do not use these members in
renderer side blah blah.."

[Tom Sepez, 2017/05/09 17:37:25]

I'm not sure the comment is helpful.  I'm also not sure what you mean by "only
used browser side".  If so, why are they being passed across mojo?

[zino, 2017/05/10 17:54:42]

I removed these members in mojom and then add a new struct in public directory.
(payment_instrument.h and .cc)

So, there is no mojom change in this patch.

+  string? instrument_key;
+  url.mojom.Url origin;
   string name;
   array<string> enabled_methods;
   string stringified_capabilities;
 };
 
 interface PaymentManager {
   Init(string service_worker_scope);
   SetManifest(PaymentAppManifest payment_app_manifest)
       => (PaymentAppManifestError error);
   GetManifest()
@@ skipping 24 matching lines @@
   string method_name;
   string stringified_details;
 };
 
 // This interface is provided to pass a payment app response from payment
 // request event in renderer side to browser side by calling respondWith().
 interface PaymentAppResponseCallback {
   OnPaymentAppResponse(PaymentAppResponse response,
                        mojo.common.mojom.Time dispatch_event_time);
 };