Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452)

Well, it's nullable, so I assume it was meant to be null in at least some situation.... and when requestShipping = false seems like a good guess as to when that was. I don't have a strong opinion myself, but it kind of makes sense as null in that case. @rsolomakhin, 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/browser-payment-api/pull/452#issuecomment-285215625

Received on Thursday, 9 March 2017 00:31:13 UTC