Intent to deprecate: PaymentAddress.languageCode

[Rouslan Solomakhin]

Contact emails

rou...@chromium.org

Spec

https://w3c.github.io/payment-request/#languagecode-attribute

Summary

We intend to deprecate PaymentAddress.languageCode, which is browser's best guess for the language of the text in the shipping, billing, delivery, or pickup address in Payment Request API. 

Motivation

The language of an address text is useful for choosing the right address formatting rules, but determining the language of any text can be done without user agent help. A W3C review of Chrome's existing language guessing heuristics revealed they were subpar.

Relevant discussions:

https://github.com/w3c/payment-request/issues/608

https://github.com/w3c/payment-request/pull/764

Interoperability risk

Firefox: Removed languageCode.

Edge: No public signals

Safari: Removed languageCode.

Web developers: No signals

Compatibility risk

Usage counter for languageCode shows no usage of this field on the web.

Ongoing technical constraints

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no.

Yes

OWP launch tracking bug

https://crbug.com/877521

Link to entry on the Chrome Platform Status https://www.chromestatus.com/feature/4992562146312192

Requesting approval to remove?

No. Going to add a deprecation warning first, wait a couple of months, then will request approval to remove here.

[Daniel Bratell]

We don't really do deprecations without a removal date anymore. Devtools won't even display deprecation warnings unless there is a documented removal date. The reason for that is in short that nobody takes deprecations without a date seriously, and they tend to not even be serious deprecations, just hopeful attempts to steer web developers away from some function web developers find useful.

It's always possible to revert or delay the deprecate+remove later if the date turns out to be badly chosen, so just pick the best target milestone for removal you can think of.

> Usage counter for languageCode shows no usage of this field on the web.

This indicates you might even go for a quick removal without deprecation to avoid anyone starting to use it.

/Daniel

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMMzaWEtFr2X9SbRmVVEhs9Gbs%2BL8uHJ_qd2TKdmV4qO%3DS3g0g%40mail.gmail.com.

--

/* Opera Software, Linköping, Sweden: CEST (UTC+2) */

[Rouslan Solomakhin]

Thank you for the advice! My plan was to remove in M74.

[Philip Jägenstedt]

LGTM1 to deprecate now and remove in M74. As Daniel said, if we run into trouble/breakage, we can change reconsider.

The use counter for this is https://www.chromestatus.com/metrics/feature/timeline/popularity/2542.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMMzaWE%2B%2B3kojmcq%2B6jUm3XZNS5Ed5GDE4AC0p5kPqNuJ%2BUXAA%40mail.gmail.com.

[Daniel Bratell]

LGTM2 to that plan (deprecation and removal in M74).

Please update https://www.chromestatus.com/feature/4992562146312192 with that plan too. It will form the basis for the blog post eventually so it should be correct and informative.

/Daniel

[Rouslan Solomakhin]

Updated the feature status page.

[Yoav Weiss]

LGTM3

On Thu, Oct 25, 2018 at 7:13 PM Rouslan Solomakhin <rou...@chromium.org> wrote:

Updated the feature status page.

On Wed, Oct 24, 2018 at 5:10 AM Daniel Bratell <bra...@opera.com> wrote:

LGTM2 to that plan (deprecation and removal in M74).

Please update https://www.chromestatus.com/feature/4992562146312192 with that plan too. It will form the basis for the blog post eventually so it should be correct and informative.

/Daniel

On Wed, 24 Oct 2018 07:54:36 +0200, Philip Jägenstedt <foo...@chromium.org> wrote:

LGTM1 to deprecate now and remove in M74. As Daniel said, if we run into trouble/breakage, we can change reconsider.

The use counter for this is https://www.chromestatus.com/metrics/feature/timeline/popularity/2542.

That flat-line is encouraging.

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMMzaWExWCJnZS%3DiYK8fTPojbH10L0i6nEDYznH8RvWSvCDGtQ%40mail.gmail.com.