[w3c/payment-request] the user interface's language should not be derived from `the body element` (#895) from Janice Shiu on 2020-01-23 (public-webpayments-specs@w3.org from January 2020)

From: Janice Shiu <notifications@github.com>
Date: Thu, 23 Jan 2020 02:23:18 -0800
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/issues/895@github.com>

From the payment request spec, 
https://github.com/w3c/payment-request/blob/fe208dba28724d0a316bf706fbf39cc4414bd8f2/index.html#L1094-L1097
[The body element](https://html.spec.whatwg.org/multipage/dom.html#the-body-element-2)'s definition states "The body element of a document is the first of the html element's children that is either a body element or a frameset element, or null if there is no such element."

Thus,
* `<body>` is a node can can have a language
* `<frameset>` is a node
* `null` is not a node and cannot have a language.

In [this PR](https://github.com/whatwg/html/pull/5228), @annevk states
> I'm not sure I support the use case. Other APIs, e.g., the notification API, have no such defaulting and have explicit support for language annotation. And especially for the frameset case it seems that it's highly likely it might not match the language of the application anyway.

Thus, the user interface's language should not be derived from "the body element". The spec could probably include explicit support for language annotation the way the [notification API does it](https://notifications.spec.whatwg.org/#language).

cc @marcoscaceres 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/895

Received on Thursday, 23 January 2020 10:23:20 UTC