-
Notifications
You must be signed in to change notification settings - Fork 8
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
Matching ContactAddress fields to autofill attributes #71
Comments
@marcoscaceres, @danyao, @rsolomakhin, @romandev, @aestes comments welcome! |
From the top of my head:
There's no separate field for
CEDEX is one type of sorting code. It may be the only type. I'm not 100% certain. |
@rsolomakhin Thank you very much! Maybe this could be mentioned in a non-normative section of the spec. |
Just a small correction: the note actually says the Thanks! |
As you said, |
Yeah… In the context of a PWA using the Payment Handler API, the address input may rely on web forms annotated with Now, I am assuming that the reasoning behind fixing semantics in (That the Contact Picker API reuses |
Noting duplicate of w3c/payment-request#505. |
This issue was raised in Payment Request, but closed once we removed addresses from that API. Since the features are now part of Contact Picker, we are transferring the issue here. |
Hi, can this issue be closed? It appears the question[1] was answered. [1] Question was "Is there a suggested mapping between the two?". |
@rsolomakhin Sure. |
Hi,
There is no clear mapping between the fields of
PaymentAddress
and the values accepted by theautocomplete
attribute for shipping and billing addresses:PaymentAddress
uses descriptive semantics whileautocomplete
leaves the semantics open to regional variations. Is there a suggested mapping between the two?Thank you.
The text was updated successfully, but these errors were encountered: