KEMBAR78
Clarify retry() when errorFields are not passed by marcoscaceres · Pull Request #825 · w3c/payment-request · GitHub
Skip to content

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Jan 16, 2019

closes #792

The following tasks have been completed:

  • Confirmed there are no ReSpec errors/warnings.
  • Modified Web platform tests - already tested.
  • Modified MDN Docs - not required.
  • Has undergone security/privacy review - not required.

Implementation commitment:

  • Safari - already supports behavior.
  • Chrome - already supports behavior
  • Firefox - firefox supports behavior.
  • Edge (public signal)

Optional, impact on Payment Handler spec?

None.


Preview | Diff

ianbjacobs and others added 2 commits January 17, 2019 10:58
Co-Authored-By: marcoscaceres <marcos@marcosc.com>
Co-Authored-By: marcoscaceres <marcos@marcosc.com>
@marcoscaceres
Copy link
Member Author

Thanks for the speedy review, @rsolomakhin!

@marcoscaceres marcoscaceres merged commit 5459933 into gh-pages Jan 17, 2019
@marcoscaceres marcoscaceres deleted the retry_empty branch January 17, 2019 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

consider requiring an error (non-empty dict) for .retry()?

3 participants