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

I agree, but this applies broadly to the whole specification. Basically anywhere a DOM Excpetion is thrown, text should be followed by:

> throw a WhatEverException, optionally informing the developer that < description of what happened >. 

Which basically we can hook into .message without being overly prescriptive (and allowing for localization of errors, etc.) . 

 Also, it's nice to drop "author" in favor of developer. Author sounds antiquated nowadays. 


-- 
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-260227262