Intent to Prototype: Secure Payment Confirmation: Locale Validation

[Chromestatus]

Contact emails

darwi...@chromium.org

Explainer

https://github.com/w3c/secure-payment-confirmation/issues/343

Specification

https://w3c.github.io/secure-payment-confirmation/#dom-securepaymentconfirmationrequest-locale

Design docs

https://github.com/w3c/secure-payment-confirmation/issues/343

Summary

Updates Secure Payment Confirmation's `locale` data field to return a Javascript TypeError if none of the language tags provided in the field match the language used by the Secure Payment Confirmation's dialog. If the field is not set or empty, this validation is skipped. This helps web developers with matching the language of the data that they are supplying to Secure Payment Confirmation with the dialog.

Blink component

Blink>Payments

Web Feature ID

secure-payment-confirmation

Motivation

This feature amends Secure Payment Confirmation so that web developers can align the language of data elements that they supply to Secure Payment Confirmation with the language used by the Secure Payment Confirmation dialog. Currently web developers can provide a list of language tags for Secure Payment Confirmation to use in their dialog. But Secure Payment Confirmation does not use this list because it is not feasible for the browser to support all languages and the Secure Payment Confirmation is a browser feature so it should use the browser language to be consistent with other browser features. By returning an error when none of the language tags provided match Secure Payment Confirmation's language, web developers are able to retry with different language tags (while updating the language of their supplied data elements) until they get a match.

Initial public proposal

https://github.com/w3c/secure-payment-confirmation/issues/343

Search tags

spc

Goals for experimentation

None

Requires code in //chrome?

False

Tracking bug

https://crbug.com/535278878

Launch bug

https://launch.corp.google.com/launch/4489220

Measurement

A new SecurePaymentConfirmation.LocaleOutcome will be created and used to track the usage and outcomes (match vs no-match) of the field.

Availability expectation

The locale validation for Secure Payment Confirmation will only be available in Chromium browsers for the foreseeable future.

Estimated milestones

Shipping on desktop	154
Shipping on Android	154

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5126146013396992?gate=5876423777714176

This intent message was generated by Chrome Platform Status.