From 81b3240a046ce70004ef3f0f2ba6e45734c583c8 Mon Sep 17 00:00:00 2001
From: Manu Sporny
Buying things on the @@ -133,50 +133,50 @@
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: -
-- A user agent MUST behave as described in this specification +
+ This specification defines one class of products: +
++ 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]] +
+ +- This specification relies on several other underlying specifications. -
-+ This specification relies on several other underlying specifications. +
+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 @@ 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 theshippingOption
attribute on request to null.
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.
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.
PaymentRequest
called request with an event name of name.
- It MUST run the following steps:
+It MUST run the following steps:
+// 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:
-// 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: