Separate PaymentRequest initialization and display.

third_party/WebKit/public/platform/modules/payments/payment_request.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.
 
 [JavaPackage="org.chromium.mojom.payments"]
 module blink.mojom;
 
 // The shipping address that the browser process provides to the renderer
 // process. Built either by the browser or a payment app.
 struct PaymentAddress {
@@ skipping 113 matching lines @@
 };
 
 enum PaymentComplete {
   SUCCESS,
   FAIL,
   UNKNOWN
 };
 
 interface PaymentRequest {
   SetClient(PaymentRequestClient client);
-  Show(array<PaymentMethodData> methodData,
+  Init(array<PaymentMethodData> methodData,

[Marijn Kruisselbrink, 2016/08/22 16:46:15]

Would it make sense to pass the PaymentRequestClient also as part of the Init
call? Not sure what the reasons for keeping it separate/merging them would be.

[please use gerrit instead, 2016/08/22 16:49:32]

Good idea. I'm on it.

        PaymentDetails details,
        PaymentOptions options);
+  Show();
   UpdateWith(PaymentDetails details);
   Abort();
   Complete(PaymentComplete result);
 };