Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / w3c/payment-request issues and pull requests

#836 - Add regionCode attribute to PaymentAddress (1.1)

Pull Request - State: closed - Opened by marcoscaceres about 6 years ago - 9 comments
Labels: do not merge yet

#828 - Do .data IDL conversion in constructor

Pull Request - State: closed - Opened by marcoscaceres about 6 years ago

#823 - Remove regionCode attribute

Pull Request - State: closed - Opened by marcoscaceres about 6 years ago - 3 comments

#817 - Extensibility of PaymentResponse.complete(result)

Issue - State: open - Opened by adrianhopebailie about 6 years ago - 9 comments
Labels: Extensibility, proposal - needs discussion, Future Candidate Feature, SRC

#772 - Extract actionable items from Shopify study

Issue - State: closed - Opened by marcoscaceres over 6 years ago - 2 comments

#710 - Clarify that empty region/regionCode is ok for some locales

Issue - State: closed - Opened by marcoscaceres almost 7 years ago
Labels: Editorial

#705 - Retrying a payment

Issue - State: closed - Opened by marcoscaceres almost 7 years ago - 14 comments
Labels: CR-Exit, Has Pull Request

#701 - Alternative 'Pay' button wording options for Browser UI (the button in the sheet)

Issue - State: open - Opened by hexalys almost 7 years ago - 14 comments
Labels: Future Candidate Feature

#690 - Add regionCode attribute

Pull Request - State: closed - Opened by marcoscaceres almost 7 years ago - 13 comments

#683 - Editorial: describe security mitigations #675

Pull Request - State: closed - Opened by ianbjacobs about 7 years ago - 6 comments
Labels: Blocked

#677 - Add latitude and longitude to PaymentAddress interface?

Issue - State: closed - Opened by stpeter about 7 years ago
Labels: proposal - needs discussion, Future Candidate Feature

#661 - Add Crypto Currency (BTC, ETH) as supported method

Issue - State: closed - Opened by buhrmi about 7 years ago - 1 comment

#654 - add redactList for PaymentAddress (Part 1)

Pull Request - State: closed - Opened by marcoscaceres over 7 years ago - 20 comments

#653 - Merchant-specified default shipping address

Issue - State: open - Opened by rsolomakhin over 7 years ago - 16 comments
Labels: Future Candidate Feature, PaymentAddress

#650 - Allow locale to be specified by the developer.

Issue - State: open - Opened by michelle over 7 years ago - 18 comments
Labels: i18n-tracker, Future Candidate Feature, Has Pull Request

#641 - Extract actionable items from @lknik's review

Issue - State: closed - Opened by marcoscaceres over 7 years ago - 3 comments

#615 - Pre-calculate shipping costs for available addresses

Issue - State: open - Opened by dandv over 7 years ago - 2 comments
Labels: enhancement, proposal - needs discussion, Future Candidate Feature

#614 - Pre-filter shipping addresses, e.g. by country

Issue - State: open - Opened by dandv over 7 years ago - 5 comments
Labels: Future Candidate Feature, PaymentAddress

#574 - Editorial: change around payment handler language (closes #532)

Pull Request - State: closed - Opened by ianbjacobs over 7 years ago - 2 comments

#548 - Adding custom fields next after shipping options have been added.

Issue - State: open - Opened by mustafa-x over 7 years ago - 11 comments
Labels: Future Candidate Feature

#544 - updateWith() "InvalidStateError" DOMException

Issue - State: closed - Opened by marcoscaceres over 7 years ago - 2 comments
Labels: question

#537 - Shipping Address Validation - Suggest Alternate Address

Issue - State: open - Opened by ktmitton over 7 years ago - 12 comments
Labels: enhancement, question, Future Candidate Feature

#505 - Provide better mapping between PaymentAddress and HTML5 autofill

Issue - State: closed - Opened by marcoscaceres almost 8 years ago - 8 comments
Labels: question, Editorial

#480 - Add payerGivenName + payerFamilyName to PaymentAddress

Issue - State: closed - Opened by marcos-travel almost 8 years ago - 23 comments
Labels: i18n-tracker, Future Candidate Feature, PaymentAddress

#471 - Recipient and payerName are lacking i18n support

Issue - State: closed - Opened by nickjshearer almost 8 years ago - 4 comments
Labels: i18n-tracker

#389 - PaymentRequest does not handle the case of store pickup

Issue - State: open - Opened by sanjoypal about 8 years ago - 16 comments
Labels: enhancement, Core Functionality, Design/Technical, Future Candidate Feature

#327 - Add dir/lang member on dictionaries whose content is displayed in browser UI

Issue - State: closed - Opened by marcoscaceres about 8 years ago - 20 comments
Labels: Core Functionality, Priority: Postponed, i18n-needs-resolution

#195 - Terms and conditions next to "Pay" button

Issue - State: closed - Opened by rsolomakhin almost 9 years ago - 8 comments
Labels: question, Design/Technical, Priority: Low

#154 - Should the browser API support the concept of "messages"?

Issue - State: closed - Opened by adrianhopebailie almost 9 years ago - 15 comments
Labels: question, Design/Technical, Priority: Medium

#145 - Support for gift cards and discount codes

Issue - State: open - Opened by andrewpaliga almost 9 years ago - 33 comments
Labels: proposal - needs discussion, Future Candidate Feature