- From: Danyao Wang <notifications@github.com>
- Date: Tue, 12 May 2020 08:41:38 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 12 May 2020 15:41:50 UTC
> We have a patch ready to go on the Firefox side... @edenchuang was also wondering what we should do about duplicate payment method modifiers for the same PMI... we have a last one wins algo there, the maybe we should start throwing for those too (we can do that as a followup). I went to look for why we decided on "last one wins" before and found these two threads: https://github.com/w3c/payment-request/issues/684 https://github.com/w3c/payment-request/pull/581 IIUC, the main thrust for supporting multiple modifiers for the same PMI is because of `basic-card`. A merchant may want to specify a different modifier for different `supportedNetworks` of `basic-card`. While I think it'll be conceptually cleaner if the spec treats method data and method modifier consistently, the `basic-card` use case seems legitimate. So I think we should keep the current "last one wins" algorithm and not throw. -- 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-request/pull/908#issuecomment-627424906
Received on Tuesday, 12 May 2020 15:41:50 UTC