KEMBAR78
Warn when errorFields don't match request[[options]] by marcoscaceres · Pull Request #807 · w3c/payment-request · GitHub
Skip to content

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Nov 15, 2018

closes #793

The following tasks have been completed:

Implementation commitment:

Optional, Impact on Payment Handler spec?


Preview | Diff

@marcoscaceres
Copy link
Member Author

@rsolomakhin, would mind having a first look?

@marcoscaceres
Copy link
Member Author

marcoscaceres commented Nov 27, 2018

Added manual test web-platform-tests/wpt#14246

@marcoscaceres
Copy link
Member Author

Anyone else willing to support these warnings (as we discussed in #793)? @aestes, @rsolomakhin?

Copy link
Collaborator

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with question

@marcoscaceres
Copy link
Member Author

marcoscaceres commented Nov 28, 2018

@rsolomakhin, filed Chrome bug. Hope that's ok, based on discussion.

@marcoscaceres marcoscaceres merged commit 4937ad2 into gh-pages Dec 2, 2018
@marcoscaceres marcoscaceres deleted the warnings branch December 2, 2018 02:57
aarongable pushed a commit to chromium/chromium that referenced this pull request Dec 5, 2018
Related spec change:
  w3c/payment-request#807

Test:
  web-platform-tests/wpt#14246

Bug: 909577
Change-Id: Idb4caa2ad08193decaf1d4b0b0435e958176929b
Reviewed-on: https://chromium-review.googlesource.com/c/1359932
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#613788}
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.

Should we validate nonsense payer error properties?

3 participants