You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible that HTML should actually export a term for the thing that winds up in navigator.language, instead of making other specs repeat the phrase that defines it.
The text was updated successfully, but these errors were encountered:
But it looks like this data is coming from some OS API which is probably (like navigator.language?) configured by the user, instead of document's language which can be configured by the developer. So local-font-access is correct and indeed wants the kind of hook you mention.
Since @inexorabletash's WICG/local-font-access#76, https://wicg.github.io/local-font-access/#user-language is now defined as "either a plausible language or the user’s most preferred language", but "a plausible language" isn't exported from HTML. It's not urgent, but it'd be good for HTML to export the terms that other specs want to use, or for us to pick something else to reference from that other spec.
It's possible that HTML should actually export a term for the thing that winds up in
navigator.language
, instead of making other specs repeat the phrase that defines it.The text was updated successfully, but these errors were encountered: