From 81b3240a046ce70004ef3f0f2ba6e45734c583c8 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Mon, 14 Mar 2016 15:39:00 -0400 Subject: [PATCH 1/3] Remove trailing whitespace. --- specs/paymentrequest.html | 76 +++++++++++++++++++-------------------- 1 file changed, 38 insertions(+), 38 deletions(-) diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html index d5160f90..837cc43e 100644 --- a/specs/paymentrequest.html +++ b/specs/paymentrequest.html @@ -89,7 +89,7 @@ Web Platform Incubator Community Group.

- +

Introduction

Buying things on the @@ -133,50 +133,50 @@

Non-goals

- +

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

-

- This specification defines one class of products: -

-
-
Conforming user agent
-
-

- A user agent MUST behave as described in this specification +

+ This specification defines one class of products: +

+
+
Conforming user agent
+
+

+ A user agent MUST behave as described in this specification in order to be considered conformant. In this specification, user agent means a Web browser or other interactive user agent as defined in [[!HTML5]]. -

-

- User agents MAY implement algorithms given in this - specification in any way desired, so long as the end result is - indistinguishable from the result that would be obtained by the - specification's algorithms. -

-

- A conforming Payment Request API user agent MUST also be a - conforming implementation of the IDL fragments - of this specification, as described in the - “Web IDL” specification. [[!WEBIDL]]

- - +

+ User agents MAY implement algorithms given in this + specification in any way desired, so long as the end result is + indistinguishable from the result that would be obtained by the + specification's algorithms. +

+

+ A conforming Payment Request API user agent MUST also be a + conforming implementation of the IDL fragments + of this specification, as described in the + “Web IDL” specification. [[!WEBIDL]] +

+ +
-
-

Dependencies

-

- This specification relies on several other underlying specifications. -

-
+
+

Dependencies

+

+ This specification relies on several other underlying specifications. +

+
Payment Request Document Architecture
The terms Payment Method, Payment App, and Payment Transaction @@ -200,7 +200,7 @@

Dependencies

be serialized to a string using JSON.stringify and later deserialized back to an object using JSON.parse with no loss of data.

-
DOM4
+
DOM4
The Event type and the terms fire an event, dispatch flag, stop propagation flag, and stop immediate propagation flag are defined by [[!DOM4]]. @@ -249,7 +249,7 @@

PaymentRequest interface

user agent while the user is providing input before approving or denying a payment request.

-

The following example shows how to construct a PaymentRequest and begin the +

The following example shows how to construct a PaymentRequest and begin the user interaction:

@@ -408,7 +408,7 @@ 
PaymentRequest constructor

             Set the value of the shippingOption attribute on request to null.
           
           
  • 
-            If details contains a shippingOptions sequence with a 
+            If details contains a shippingOptions sequence with a
             length of 1, then set shippingOption to the id of
             the only ShippingOption in the sequence.
           
    • 
@@ -938,7 +938,7 @@ 
    PaymentRequestUpdateEvent
    
               
               
  • Let newOption be null.
    • 
               
  • 
-                If details contains a shippingOptions sequence with a 
+                If details contains a shippingOptions sequence with a
                 length of 1, then set newOption to the id of the only
                 ShippingOption in the sequence.
               
    • 
@@ -1013,7 +1013,7 @@ 
    PaymentRequest updated algorithm
    
           The PaymentRequest updated algorithm is run by other algorithms above to fire
           an event to indicate that a user has made a change to a PaymentRequest
           called request with an event name of name.
    
-        
    It MUST run the following steps:
     
+        
    It MUST run the following steps:
    
         
      
           
    1. 
             If the request@[[\updating]] is true, then terminate

From 3ddca06a9e2a7734809012ef55a21ea1671d8fb5 Mon Sep 17 00:00:00 2001
From: Manu Sporny 
Date: Wed, 16 Mar 2016 12:56:35 -0400
Subject: [PATCH 2/3] Add reference to issue #47.

---
 specs/paymentrequest.html | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index 837cc43e..625330b9 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -249,6 +249,30 @@ 
      PaymentRequest interface
      
         user agent while the user is providing input before approving or denying a payment request.
       
      
 
+      
      
+        Instead of a programmable object, it has been suggested that a payment
+        request should be just pure data that can be operated on by methods
+        like so:
+        
      +// data-only payment request object example
+var request = {
+  type: 'PaymentRequest',
+  description: 'Payment to ExampleMerch for widgets',
+  acceptablePayment: {
+    paymentMethod: 'Visa',
+    paymentAmount: {
+      amount: '4.35',
+      currency: 'USD'
+    }
+  }
+};
+
+// request payment and get a promise that will resolve to
+// a payment acknowledgement
+var payment = navigator.payment.request(request);
+        
      
+      
      
+
       
      The following example shows how to construct a PaymentRequest and begin the
       user interaction:
      
 

From 2eef63459b2379f9343d2df6acc9b19bada456b3 Mon Sep 17 00:00:00 2001
From: Manu Sporny 
Date: Tue, 29 Mar 2016 17:16:09 -0400
Subject: [PATCH 3/3] Simplify reference to issue #47.

---
 specs/paymentrequest.html | 30 ++++++------------------------
 1 file changed, 6 insertions(+), 24 deletions(-)

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index 625330b9..615a79c8 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -249,30 +249,6 @@ 
      PaymentRequest interface
      
         user agent while the user is providing input before approving or denying a payment request.
       
      
 
-      
      
-        Instead of a programmable object, it has been suggested that a payment
-        request should be just pure data that can be operated on by methods
-        like so:
-        
      -// data-only payment request object example
-var request = {
-  type: 'PaymentRequest',
-  description: 'Payment to ExampleMerch for widgets',
-  acceptablePayment: {
-    paymentMethod: 'Visa',
-    paymentAmount: {
-      amount: '4.35',
-      currency: 'USD'
-    }
-  }
-};
-
-// request payment and get a promise that will resolve to
-// a payment acknowledgement
-var payment = navigator.payment.request(request);
-        
      
-      
      
-
       
      The following example shows how to construct a PaymentRequest and begin the
       user interaction:
      
 
@@ -365,6 +341,12 @@ 
      PaymentRequest constructor
      
           currently described in the specification.
         
 
+        
      
+          There is an open issue about whether the payment request should
+          be a programmable object or should be just pure data that can be
+          operated on by methods.
+        
      
+
         
      
           There is an open issue about whether the API should handle occasions when a site wants to request a payment
           method but not actually make a charge immediately. These may include identification validation, pre-auth