My understanding of the consensus that has emerged through discussion of PR API issue 684 [1] is that each specification should define its own approach to resolving duplicate instances of modifiers, and that payment method specifications should favor a "last one wins" approach. As I understand it, this is the approach taken by current implementations of Basic Card. I am raising an issue here so that we can close issue 684 on PR API more quickly (with an informative note in that specification). @marcoscaceres has indicated he would work on the text in Basic Card to capture the "last one wins" approach. However, we propose to wait until resolving issue #59 because the algorithm will be simpler if we drop supportedTypes. [1] https://github.com/w3c/payment-request/issues/684#issuecomment-405612400 -- 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/payment-method-basic-card/issues/60
Received on Friday, 21 September 2018 15:37:09 UTC