From 41f8151a0d8c30398bf3437db2a917a254ba413a Mon Sep 17 00:00:00 2001 From: Ade Bateman Date: Thu, 28 Apr 2016 15:12:16 -0700 Subject: [PATCH] Fix old reference to items and use total/displayItems --- specs/paymentrequest.html | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html index 6a46ec7e..63e39be7 100644 --- a/specs/paymentrequest.html +++ b/specs/paymentrequest.html @@ -389,10 +389,6 @@

PaymentRequest constructor

have a legitimate reason to request payment.

-
  • - If details does not contain a sequence of items with length greater - than zero, then throw a TypeError. -
  • For each PaymentMethodData in methodData, if the data field is supplied but is not a JSON-serializable object, then throw a TypeError. @@ -683,11 +679,6 @@

    PaymentDetails dictionary

    of this option without running the shipping option changed algorithm.

    - -
    - There is an open issue about whether the items sequence should special-case the last - item in the sequence to represent the total. -
    @@ -1006,8 +997,12 @@

    PaymentRequestUpdateEvent

    PaymentDetails dictionary, then:
    1. - If details contains an items value, then copy - this value to the items field of target@[[\details]]. + If details contains a total value, then copy + this value to the total field of target@[[\details]]. +
    2. +
    3. + If details contains a displayItems value, then copy + this value to the displayItems field of target@[[\details]].
    4. If details contains a shippingOptions sequence, then