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 ce5c8956bec2776c8b71a1c7a8d3290d86434a88 Mon Sep 17 00:00:00 2001
From: Manu Sporny 
Date: Wed, 16 Mar 2016 12:18:05 -0400
Subject: [PATCH 2/3] Add reference to issue #39.

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

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index 837cc43e..170d0761 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -459,6 +459,18 @@ 
      show()
      
             later be resolved by the user accepts the payment request algorithm through interaction with the user interface.
           
      2. 
         
    
+
+
+        
    
+          How do we support Web-based payment apps? These instruments require
+          a user to: 
    
+          1. Start on the merchant website
    
+          2. Click buy
    
+          3. Select the web-based instrument
    
+          4. Navigate to a 3rd party website to approve the transaction
    
+          5. Return to the merchant website with a token, approval code, or
+          other proof that the transaction has been approved.
+
    From 559a706a70cc68f47e1d7f15ec9bc5e609c1b369 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 29 Mar 2016 17:24:59 -0400 Subject: [PATCH 3/3] Update reference to issue #39. --- specs/paymentrequest.html | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html index 170d0761..7704c895 100644 --- a/specs/paymentrequest.html +++ b/specs/paymentrequest.html @@ -459,18 +459,6 @@

    show()

    later be resolved by the user accepts the payment request algorithm through interaction with the user interface. - - -

    - How do we support Web-based payment apps? These instruments require - a user to:
    - 1. Start on the merchant website
    - 2. Click buy
    - 3. Select the web-based instrument
    - 4. Navigate to a 3rd party website to approve the transaction
    - 5. Return to the merchant website with a token, approval code, or - other proof that the transaction has been approved. -

    @@ -1055,6 +1043,7 @@

    User agent delegates payment request algorithm

    only available for a limited amount of time. If the user does not accept the payment request within the allowed time period, then the request will be aborted.

    +

    A user agent may not always be able to abort a request. For example, if the user agent has delegated responsibility for the request to another app. To support this situation, @@ -1082,6 +1071,14 @@

    User agent delegates payment request algorithm

    +

    + The architecture document suggests that payment apps may take + numerous forms, including as web-based apps. This specification + should describe how the user-agent will pass the payment request + data and the complete signal to a web-based payment app and also how + it will receive the payment response from the payment app. +

    +

    We believe there are user agent configurations that can cause the UI to get into a state where cancellation by the web page during user interaction is difficult. Users should still