- From: Matt N. <notifications@github.com>
- Date: Tue, 13 Feb 2018 17:12:44 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 February 2018 19:23:04 UTC
Not sure how I didn't find #309 in my search… It looks like duplicate PMIs were disallowed while working on #581 (which I don't think is a good solution and it seemed others agree) but that text was removed in https://github.com/w3c/payment-request/pull/581/commits/5e6ca6da68bd65634a309662c067c3b83eed97fc before merging. It seems like #581 then didn't end up addressing the issue. There was some talk about having the first match win but I'll note that shippingOptions work in the opposite way… the last `selected` wins: > If more than one item in the sequence has selected set to true, then the user agent selects the last one in the sequence. I think we should be consistent on first vs. last in tie breaker scenarios. -- 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/issues/684#issuecomment-365335925
Received on Tuesday, 13 February 2018 19:23:04 UTC