From 029d1aa9ec13a430fd193d5bddf2d520f124acef Mon Sep 17 00:00:00 2001 From: Marcos Caceres Date: Thu, 27 Apr 2017 11:58:38 +1000 Subject: [PATCH] editorial: s/target/request in updateWith() algo Makes this algorithm consistent with other algorithms. Also avoids having to backtrack to check the type of "target". --- index.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index 6d3f422e..e9effec6 100644 --- a/index.html +++ b/index.html @@ -2033,10 +2033,10 @@

  • Let event be this PaymentRequestUpdateEvent instance.
    • -
  • Let target be the value of event's +
  • Let request be the value of event's target attribute.
    • -
  • If target is not a PaymentRequest object, +
  • If request is not a PaymentRequest object, then throw a TypeError.
  • If the dispatch flag is unset, then throw an @@ -2045,11 +2045,11 @@

  • If event.[[\waitForUpdate]] is true, then throw an "InvalidStateError" DOMException.
    • -
  • If target.[[\state]] is not +
  • If request.[[\state]] is not "interactive", then throw an "InvalidStateError" DOMException.
    • -
  • If target.[[\updating]] is true, then +
  • If request.[[\updating]] is true, then throw an "InvalidStateError" DOMException.
  • Set event's stop propagation flag and stop @@ -2057,7 +2057,7 @@

  • Set event.[[\waitForUpdate]] to true.
    • -
  • Set target.[[\updating]] to true. +
  • Set request.[[\updating]] to true.
  • The user agent SHOULD disable the user interface that allows the user to accept the payment request. This is to ensure