- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 06 Feb 2018 09:52:27 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 6 February 2018 09:52:52 UTC
This doesn't affect the spec - it's mostly around best practice. Interesting question came up from @mnoorenberghe over in Mozilla's [bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1432909): Should a merchant include the shipping option as a `displayItem` even though it's already included as a separate thing? The risk being that if it's included twice, the amounts might fall out of sync. @rsolomakhin states that merchants have been including the selected shipping option as a display item in a lot of cases. I personally don't think they should (as it's redundant, and in Firefox's UI, at least, we call out shipping clearly), but this might be different for other implementations. Thus, in Firefox, it might look weird if a vendor includes shipping as a display item, because we will also show it when we list everything being paid for: ![screenshot 2018-02-06 20 49 05](https://user-images.githubusercontent.com/870154/35852502-2fcb3312-0b7f-11e8-8d72-825e2fcf4b36.png) Thoughts? -- 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/680
Received on Tuesday, 6 February 2018 09:52:52 UTC