Skip to content

Commit

Permalink
Remove issue #48 label.
Browse files Browse the repository at this point in the history
Fixes #48.

PR #162 refactored the supportedMethods and payment specific data
fields. Issue #3 discusses supporting multiple currencies and issue #4
discusses price per payment method and we should consider specific
proposals for those issues.

PR #162 replaces the `sequence<DOMString>` with
`sequence<PaymentMethodData>` so we now use objects.
  • Loading branch information
adrianba committed Apr 28, 2016
1 parent acf1150 commit 63d1aa6
Showing 1 changed file with 0 additions and 6 deletions.
6 changes: 0 additions & 6 deletions specs/paymentrequest.html
Original file line number Diff line number Diff line change
Expand Up @@ -351,12 +351,6 @@ <h2>PaymentRequest constructor</h2>
for a deposit, pre-auth for a later payment, making recurring payments, and more.
</div>

<div class="issue" data-number="48" title="Should list of accepted payment methods be strings or objects?">
There is an open issue about whether the list of supported payment
methods should be passed to the user agent as a simple sequence of
strings or as a more complex and flexible object structure.
</div>

<div class="issue" data-number="51" title="Should the payment API be more conversational or less conversational?">
There is an open issue regarding whether the current pattern of using
events for exchange of data between the user agent and the website is
Expand Down

0 comments on commit 63d1aa6

Please sign in to comment.