No means of negotiating the language/locale of the payment experience

[aphillips]

https://w3c.github.io/secure-payment-confirmation

While there are only a few strings in the the SPC spec that can contain natural language data (most fields are locale-neutral IDs of various kinds), there is no mechanism in webAuthn or in SPC to communicate the locale preference(s) of the customer or caller to the Relying Party. Such information might be needed in order to compute the language-specific URL for display as an iframe or to fill in appropriately localized versions of the display name or icon image returned.

The lack of such a mechanism seems to be an oversight.

---

Instructions:

This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. CREATE A PROPOSED REVIEW COMMENT BY REPLACING THE PROMPTS ABOVE THIS PARAGRAPH, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT Then ask the i18n WG to review your comment.

2. Set a label to identify the spec. This starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staffer to help.

3. After discussion with the i18n WG, raise this issue to the WG that owns the spec. Use the text above this para as the basis for that comment.

4. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue. Do NOT remove the initial '§ '.

5. Edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT.

6. Remove the 'pending' label.

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ link_to_issue_raised

[aphillips]

Seems like I've written this comment before--and indeed I have written it before. See, for example, here. PaymentRequest inserted this note as a result of that comment:

The API does not currently provide a way for developers to specify the language and base direction in which the payment sheet is presented to end users. Instead, the API relies on localization information inherited from the document. The working group is considering support for requesting specific localization of the user interface and of individual PaymentItems and user-facing error messages in a future version of this API.

PaymentRequest published a CR draft on 2021-09-07 (so two days ago) with that note, so I doubt we'll get a change in the current version of that, but I think this is a gap that authentication and payments should address head on before we get a lot of specs going 🤷🤷‍♂️. 😉

[aphillips]

Duplicates #1043