Skip to content

the user interface's language should not be derived from the body element #895

@janiceshiu

Description

@janiceshiu

From the payment request spec,

payment-request/index.html

Lines 1094 to 1097 in fe208db

of the user when presenting payment methods. It is RECOMMENDED that
the language of the user interface match the [=node/language=] of the
<a data-cite="HTML/dom.html#the-body-element-2">the body element</a>
element.

The body element'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, @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.

cc @marcoscaceres

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions