Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)

This seems really tough...

So given a situation where people are (as @rsolomakhin states) sending info like:

- Display items: shoes $100, shipping by drone $10
- Shipping options: by drone $10
- Total: $110

I don't see a world where you could usefully create a UI like Firefox's. It seems like you'd end up with

```
Shoes               $100
Shipping by drone   $10
------------------------
                    $110
Shipping            $10

              TOTAL $110
```

which is obviously quite confusing.

You could perhaps ask that everyone upgrade their code to include more information (e.g., include an id with every payment item/shipping option), so that Firefox could remove payment-items-that-are-actually-shipping-options from the list of items. But unless that's mandatory, you're in real trouble.

Is the goal to figure out a modification to the specification that would allow Firefox to dedupe, and hope that all sites using PaymentRequest upgrade to that? Or is to add guidance to the specification to ask developers to stop adding dupes?

(Side note: I guess it's already true that people can create confusing experiences in any browser by mismatching `total` with the sum of all the displayItems + shippingOptions + modifiers?)

-- 
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#issuecomment-365785893