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

Pre-filter shipping addresses, e.g. by country #614

Open
dandv opened this issue Sep 7, 2017 · 5 comments · Fixed by #955
Open

Pre-filter shipping addresses, e.g. by country #614

dandv opened this issue Sep 7, 2017 · 5 comments · Fixed by #955

Comments

@dandv
Copy link

dandv commented Sep 7, 2017

If a merchant only ships to certain regions, it would be useful to pre-filter the shipping addresses the user can select from. The case of no eligible address would be quite frequent - the user could see instead an explanation provided by the merchant, along with an affordance for adding an eligible address.

Example use cases:

  • Merchant doesn't ship to non-continental US, and the user has two addresses, one in Hawaii and one in California. In this case, only the California address would be shown.
@marcoscaceres
Copy link
Member

Smarter filtering would be nice. However, it would mean passing all addresses to the merchant, and that doesn't seem great from a privacy perspective...

Conversely, the merchant would need to pass in all the states for each country that they support. That could be more doable, but we would need a standardized list of all the states/provinces/regions in the world.

@dandv
Copy link
Author

dandv commented Sep 8, 2017

the merchant would need to pass in all the states for each country that they support

ISO3166 standardizes the country code. Provinces and regions are more of a can of worms, agreed, but perhaps filtering by country would cover 80% of the use cases.

@marcoscaceres
Copy link
Member

Turns out ISO3166 also does regions (things you learn 👨‍🏫).

Step 1 will be do add region codes to w3c/contact-picker#65.

@ianbjacobs
Copy link
Collaborator

This issue was raised in Payment Request, but closed once we removed addresses from that API. We anticipate adding addresses back to the specification and so are re-opening this issue proactively.

@ianbjacobs ianbjacobs reopened this Feb 12, 2024
@ianbjacobs
Copy link
Collaborator

We added addresses back to the specification in the 7 August 2024 CRD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants