- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 24 Aug 2017 18:06:03 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 25 August 2017 01:06:44 UTC
marcoscaceres commented on this pull request. > @@ -2880,9 +2893,18 @@ further action. The <a>user agent</a> user interface should ensure that this never occurs. </li> - <li> - <a>Fire an event</a> named <var>name</var> at <var>request</var> - using <a>PaymentRequestUpdateEvent</a>. + <li>Let <var>event</var> be the result of <a>fire an event</a> named + <var>name</var> at <var>request</var> using + <a>PaymentRequestUpdateEvent</a>. + </li> + <li data-link-for="PaymentRequestUpdateEvent">If + <var>event</var>.<a>[[\waitForUpdate]]</a> is true, disable any part + of the user interface that could cause another update event to be + fired. Wait for <var>event</var>.<a>updateWith()</a> method's + <var>detailsPromise</var> to settle. `.updateWith()` controls re-enabling the user interface, in step 14. It might be redundant to re-state it here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/pull/591#discussion_r135165478
Received on Friday, 25 August 2017 01:06:44 UTC