Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change how invalid lang codes are to be treated by user agents #160

Closed
stevenatkin opened this issue May 24, 2016 · 1 comment
Closed

Change how invalid lang codes are to be treated by user agents #160

stevenatkin opened this issue May 24, 2016 · 1 comment
Labels
s:html https://html.spec.whatwg.org/multipage/

Comments

@stevenatkin
Copy link

3.2.5.3 The lang and xml:lang attributes
http://www.w3.org/TR/html51/single-page.html#the-lang-and-xmllang-attributes

The specification states that invalid BCP47 language codes are to be passed to user agents, but then restricts how the invalid code is to be treated by the user agent. The spec states that if the user agent understands the invalid code and wants to interpret that as synonym for another language code then that would be incorrect. I think we should remove this restriction and simply pass the invalid code to the user agent and then allow the user agent to interpret that code any way they wish.

@stevenatkin stevenatkin added pending Issue not yet sent to WG, or raised by tracker tool & needing labels. s:html https://html.spec.whatwg.org/multipage/ labels May 24, 2016
@r12a
Copy link
Contributor

r12a commented Jun 2, 2016

During telecon decided that this is ok, since it protects the browser from having to recognise ill-formed subtags as BCP47, with possible threat after to the standard.

@r12a r12a closed this as completed Jun 2, 2016
@r12a r12a removed the pending Issue not yet sent to WG, or raised by tracker tool & needing labels. label Jun 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s:html https://html.spec.whatwg.org/multipage/
Projects
None yet
Development

No branches or pull requests

2 participants