Skip to content

Commit

Permalink
Update reference to issue w3c#50.
Browse files Browse the repository at this point in the history
  • Loading branch information
msporny committed Mar 30, 2016
1 parent 2ff1406 commit 271b3e7
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions specs/paymentrequest.html
Original file line number Diff line number Diff line change
Expand Up @@ -779,13 +779,6 @@ <h2>PaymentResponse interface</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>
A <code><dfn>PaymentResponse</dfn></code> is returned when a user has selected a payment method and
approved a payment request. It contains the following fields:
Expand Down Expand Up @@ -1087,6 +1080,13 @@ <h2>User agent delegates payment request algorithm</h2>
<a><code>abort</code></a> to account for the situation where this may fail in the <code>delegated</code>
state.</p>
</div>

<p class="issue" data-number="50" title="How are payment requests and responses passed between the browser and third-party native wallets?">
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.
</p>

</section>

<section>
Expand Down

0 comments on commit 271b3e7

Please sign in to comment.