- From: Sahel Sharify <notifications@github.com>
- Date: Wed, 25 Mar 2020 14:18:47 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 25 March 2020 21:19:00 UTC
Thanks Marcos for reviewing this! As an example Gpay is using this field to provide more details about each shipping option to their users, and they would like to have this field in payment request/handler APIs as well. Since the [shippingOptions](https://w3c.github.io/payment-handler/#shippingoptions-attribute) in PaymentRequestEvent comes from [payment details](https://www.w3.org/TR/payment-request/#dom-paymentdetailsbase) provided in PaymentRequest's [constructor](https://www.w3.org/TR/payment-request/#constructor), changing the [PaymentShippingOption](https://www.w3.org/TR/payment-request/#paymentshippingoption-dictionary) dictionary in PaymentRequest spec would be enough. ```WebIDL dictionary PaymentShippingOption { required DOMString id; required DOMString label; required PaymentCurrencyAmount amount; DOMString description; boolean selected = false; }; ``` -- 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/902#issuecomment-604092960
Received on Wednesday, 25 March 2020 21:19:00 UTC