Re: [browser-payment-api] Write-up proposal for shipping address fields (#6)

My comment wasn't really about whether this method of feature detection is crude or not but more about whether this object is the right one for developers to use for feature detection.

What this thread suggests is that developers using the payments API must initiate a payment request and request shipping data collection, then interrogate the shape of the return object that to determine what version of the payments API they are working with. I'm a firm  -1 on that.

1. This forces developers to request a user's shipping address in order to do feature detection.
1. Wouldn't developers perform their feature detection logic long before this point in the process?
1. Would changes to the API always result in measurable changes to the shape of the shipping address object so that developers can use this object as a way of detecting this?

I agree that feature detection is required but I'm not sure that the shape of this object is the right place to facilitate it.

---
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/issues/6#issuecomment-198624597