Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290)

So looking at the spec, it currently defines the message of DOM Exceptions in the Dependencies section - tailored to the payment spec. However, the errors messages are very vague right now: "the object is in a invalid state" etc. 

Admittedly, I'm not a huge fan of this approach - because it overgeneralizes each error condition. As @msporny suggests, I'd rather us take the approach where we explain why an error happened in place. 


-- 
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/290#issuecomment-260228237