diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html index d0e62dc8..1bf714ce 100644 --- a/specs/paymentrequest.html +++ b/specs/paymentrequest.html @@ -231,7 +231,7 @@

PaymentRequest interface

SecureContext] interface PaymentRequest : EventTarget { Promise<PaymentResponse> show(); - void abort(); + Promise<void> abort(); readonly attribute ShippingAddress? shippingAddress; readonly attribute DOMString? shippingOption; @@ -480,9 +480,36 @@

show()

abort()

-

The abort method may be called if the web page wishes to abort the payment - request after the show method has been called and before the request@[[\acceptPromise]] - has been resolved.

+ +

+ The abort method may be called if the web page wishes to tell the + user agent to abort the payment request and to tear down any user interface that + might be shown. abort can only be called after the show method + has been called and before the request@[[\acceptPromise]] has been resolved. + 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 might not always be able to abort a request. For example, if the user agent + has delegated responsibility for the request to another app. In this situation, abort will + reject the returned Promise. +

+ +

+ 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. +

+ +

+ This specification should describe how the user agent will pass the + payment request data and the complete signal to a native payment app + and also how it will receive the payment response from the payment app. +

The abort method MUST act as follows:

    @@ -491,9 +518,13 @@

    abort()

  1. If the value of request@[[\state]] is not interactive then throw an InvalidStateError.
    2. +
  2. Let promise be a new Promise.
    3. +
  3. Return promise and asynchronously perform the remaining steps.
    4. +
  4. Try to abort the current user interaction and close down any remaining user interface.
    5. +
  5. If it is not possible to abort the current user interaction, then reject promise + with InvalidStateError and abort this algorithm.
  6. Set the value of the internal slot request@[[\state]] to closed.
    7. -
  7. Return from the method and asynchronously perform the remaining steps.
    8. -
  8. Abort the current user interaction and close down any remaining user interface
    9. +
  9. Resolve promise with undefined.
@@ -501,7 +532,7 @@

abort()

State transitions

The internal slot [[\state]] follows the following state transitions:

Transition diagram for internal slot state of a PaymentRequest object + src="state-transitions.svg" width="518" height="125">
@@ -1159,71 +1190,6 @@

PaymentRequest updated algorithm

-
-

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 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 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: -

- -
    -
  1. - Let request be the PaymentRequest object that the user is - interacting with. -
    2. -
  2. - If the request@[[\updating]] is true, then terminate this - algorithm and take no further action. The user agent user interface should ensure - that this never occurs. -
    3. -
  3. - If the request@[[\state]] is not interactive, then terminate this - algorithm and take no further action. The user agent user interface should ensure - that this never occurs. -
    4. -
  4. - Set request@[[\state]] to delegated. -
    5. -
- -

- 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 - be able to cancel the payment but script will not be able to. We need to investigate in more - detail the consequences of this and whether it is really needed.

-

If we specify delegated then it isn't necessary for all user agents to be - able to move to this state but it would be necessary for all payment flows that wish to call - abort to account for the situation where this may fail in the delegated - state.

-
- -

- This specification should describe how the user agent will pass the - payment request data and the complete signal to a native payment app - and also how it will receive the payment response from the payment app. -

- -
-

User accepts the payment request algorithm

@@ -1242,8 +1208,8 @@

User accepts the payment request algorithm

that this never occurs.
  • - If request@[[\state]] is not interactive and - not delegated, then terminate this algorithm and take no further action. + If request@[[\state]] is not interactive, then terminate this + algorithm and take no further action. The user agent user interface should ensure that this never occurs.
  • diff --git a/specs/state-transitions.svg b/specs/state-transitions.svg index 3f6819ce..0c1ec5a4 100644 --- a/specs/state-transitions.svg +++ b/specs/state-transitions.svg @@ -1,16 +1,16 @@ - +