Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316)

We need to fix the spec everywhere for "in parallel" - so let's stick with the current text and I'll go through after and fix that after this gets merged 

> On 1 Dec. 2016, at 11:42 am, Mahesh Kulkarni <notifications@github.com> wrote:
> 
> @maheshkk commented on this pull request.
> 
> In index.html:
> 
> > +          <li>
> +            Let <var>request</var> be the <a>PaymentRequest</a> object on which the method is called.
> +          </li>
> +          <li>If the value of <var>request</var>@[[\state]] is not "created", then
> +            <a>throw</a> an <a>InvalidStateError</a>.</li>
> +          <li>
> +            Set the value of <em>request</em>@[[\state]] to "interactive".
> +          </li>
> +          <li>
> +            Let <var>acceptPromise</var> be a new <a>Promise</a>.
> +          </li>
> +          <li>
> +            Store <var>acceptPromise</var> in <em>request</em>@[[\acceptPromise]].
> +          </li>
> +          <li>
> +            Return <var>acceptPromise</var> and asynchronously perform the remaining steps.
> @marcoscaceres any pointers to "in parallel" definition Marcos? I could do another PR to add "in parallel" definition through out the spec instead.
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 


-- 
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/browser-payment-api/pull/316#issuecomment-264049079