Re: [browser-payment-api] Add a reference to issue #50. (#84)

> @@ -779,6 +779,13 @@ <h2 id="state-transitions">State transitions</h2>
>          };
>        </pre>
>  
> +      <p class="issue" data-number="50" title="How are payment requests and responses passed between the browser and third-party native wallets?">
> +        How are payment messages routed between the browser and native payment
> +        apps? The spec should give developers some idea of how the integration
> +        might happen via a NOTE or similar mechanism to ensure that people know
> +        it won't be just the OS vendors providing payment apps.
> +      </p>
> +
>        <p>

@msporny For consistency, I think the issue markers for issues #50, #39 should follow a similar format as they both relate to payment app interface (one for native apps and the other for web based apps).

I would suggest the following text and would include this at an appropriate point in the section [User Agent delegates payment request algorithm](https://w3c.github.io/browser-payment-api/specs/paymentrequest.html#user-agent-delegates-payment-request-algorithm) and possibly another reference in the [complete()](https://w3c.github.io/browser-payment-api/specs/paymentrequest.html#complete) section as this refers to messages being passed back to the payment app.

Suggested text:

```html
<p class="issue" data-number="39" title="It is unclear how the user agent will interface with 
a web-based payment app.">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.</p>
```

---
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/84/files/81b3240a046ce70004ef3f0f2ba6e45734c583c8..2ff14067b312261f1ce876b125295e651e429237#r57535654

Received on Sunday, 27 March 2016 22:23:20 UTC