https://w3c.github.io/payment-handler/#details-attribute seems to have some further text. Although it seems to have a MUST requirement to run an algorithm if the promise is rejected, but the algorithm is left completely up to implementers? That doesn't really make sense. It can't be a MUST requirement if there isn't any actually required behavior. Ah, and I guess the next paragraph is describing the behavior if the promise is resolved. Maybe the respondWith description could be extended to actually link to the spec text describing its behavior? I'm also not sure how things like failures during the structured clone (or the supposed json-serializable requirements) are supposed to be dealt with by implementations. More formal algorithmic descriptions of the behavior of respondWith would be really helpful. -- 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/payment-handler/issues/190#issuecomment-317553895
Received on Monday, 24 July 2017 21:04:34 UTC