Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16)

While more of s style argument I do think there is value in `navigator.payments` as a way of namespacing the payments functions.

Assuming we may have others like `registerPaymentApp()` in future it seems sensible to do this.

It's a personal preference and I'm open to being persuaded this is old-fashioned 

---
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/16#issuecomment-217253622