[w3c/browser-payment-api] Explain how to treat unrecognised complete values (#191)

I don't think we should make any further changes related to #122 for now. It's hard to make a trinary value fit into the promises model in an obvious way.

We should be clear on what to do with unrecognised values to allow us to add new ones in future.

Closes #122.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/191

-- Commit Summary --

  * Explain how to treat unrecognised complete values

-- File Changes --

    M specs/paymentrequest.html (5)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/191.patch
https://github.com/w3c/browser-payment-api/pull/191.diff

---
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/pull/191