Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove regionCode attribute #823

Merged
merged 3 commits into from
Jan 24, 2019
Merged

Remove regionCode attribute #823

merged 3 commits into from
Jan 24, 2019

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Jan 15, 2019

closes #816

The following tasks have been completed:

  • Confirmed there are no ReSpec errors/warnings.
  • Modified Web platform tests
  • Modified MDN Docs - going to leave docs for now, as we will bring this feature back soon.

Implementation commitment:

  • Safari - not implemented (so matches spec :)).
  • Chrome - not implemented (so matches spec :))
  • Firefox - implemented, but not really conforming. Will leave it tho, and bring it back later.
  • Edge (public signal)

Optional, impact on Payment Handler spec?


Preview | Diff

@marcoscaceres
Copy link
Member Author

CFC is going to go out later this week.

@ianbjacobs
Copy link
Collaborator

Copy link
Collaborator

@rsolomakhin rsolomakhin left a comment

Choose a reason for hiding this comment

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

LGTM if the CfC is approved.

@marcoscaceres marcoscaceres changed the title Remove PaymentAddress' regionCode attribute Remove regionCode attribute (doesn't spark joy) Jan 21, 2019
@marcoscaceres marcoscaceres changed the title Remove regionCode attribute (doesn't spark joy) Remove regionCode attribute Jan 23, 2019
@ianbjacobs
Copy link
Collaborator

@marcoscaceres marcoscaceres merged commit 5906b72 into gh-pages Jan 24, 2019
@marcoscaceres marcoscaceres deleted the remove_region_code branch January 24, 2019 20:45
aarongable pushed a commit to chromium/chromium that referenced this pull request Jan 29, 2019
The regionCode attribute was removed in spec side[1]. FYI, the attribute
was behind runtime flag and have never shipped. So, we don't need to
send intents to blink-dev.

[1] w3c/payment-request#823

Bug: 925722
Change-Id: I85b370770141b1caf69389e399358b82ad071b89
Reviewed-on: https://chromium-review.googlesource.com/c/1438981
Reviewed-by: Rouslan Solomakhin <[email protected]>
Reviewed-by: Kinuko Yasuda <[email protected]>
Commit-Queue: Jinho Bang <[email protected]>
Cr-Commit-Position: refs/heads/master@{#626895}
marcoscaceres pushed a commit that referenced this pull request Feb 21, 2019
Revert "Remove regionCode attribute (#823)"
This reverts commit 5906b72.
marcoscaceres pushed a commit that referenced this pull request Apr 10, 2019
Revert "Remove regionCode attribute (#823)"
This reverts commit 5906b72.
sideshowbarker added a commit to w3c/browser-compat-data that referenced this pull request Jan 29, 2020
queengooborg pushed a commit to mdn/browser-compat-data that referenced this pull request Jan 30, 2020
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 put regionCode attribute at risk?
4 participants