From cd80eb3090c0d6f5c6ea7f98dfd4181666b853d8 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Sun, 3 Apr 2016 11:53:39 +0900 Subject: [PATCH 1/2] =?UTF-8?q?Replace=20non-RFC-2119=20=E2=80=9Cmay?= =?UTF-8?q?=E2=80=9Ds=20in=20normative=20text?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- specs/paymentrequest.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html index fad26997..23ec2414 100644 --- a/specs/paymentrequest.html +++ b/specs/paymentrequest.html @@ -663,7 +663,7 @@

PaymentDetails dictionary

shippingOptions
- A sequence containing the different shipping options that the use may choose from. + A sequence containing the different shipping options for the user to choose from.

If the sequence is empty, then this indicates that the merchant cannot ship to the current shippingAddress.

If the sequence only contains one item, then this is the shipping option that @@ -1087,13 +1087,13 @@

User agent delegates payment request algorithm

The PaymentRequest interface allows a web page to call abort to tell the user agent to abort the payment request and to tear down any user interface that - might be shown. For example, a web page may choose to do this the goods they are selling are + might be shown. For example, a web page might choose to do this if the goods they are selling are 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 + A user agent might 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, the user agent must run the User agent delegates payment request algorithm. The algorithm MUST run the following steps: From 5fdf845cb27effda16aca58da7c3ddcb2b1af85e Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Sun, 3 Apr 2016 12:11:16 +0900 Subject: [PATCH 2/2] =?UTF-8?q?Correct=20an=20odd=20use=20of=20RFC=202119?= =?UTF-8?q?=20=E2=80=9Cmay=20not=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit “The user agent may not validate that this is true.” is not stating a normative requirement. So either the related text should be reworded in a way to state an actual normative requirement (an optional one)ーwhich is what this PR attempts to doーor the language should be changed to drop the “may” completely. --- specs/paymentrequest.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html index 23ec2414..2b1151f1 100644 --- a/specs/paymentrequest.html +++ b/specs/paymentrequest.html @@ -658,8 +658,8 @@

PaymentDetails dictionary

This sequence of PaymentItem dictionaries indicates what the payment request is for. The sequence must contain at least one PaymentItem. The last PaymentItem in the sequence represents the total amount of the payment - request. It is the responsibility of the calling code to ensure that the total amount is - the sum of the preceding items. The user agent MAY not validate that this is true. + request. The user agent MAY validate that the total amount is the sum of the + preceding items, but it is the responsibility of the calling code to ensure that.
shippingOptions