application-name language negotiation should use lookup

[aphillips]

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ whatwg/html#5245

[r12a]

This algorithm seems wrong to me, since iiuc it doesn't allow the normal matching applied during content negotiation. For example, it is unable to match ja and ja-JP, even though an informed user would use lang="ja" but many browser preferences will automatically be set to ja-JP.

Also, i think you have the wrong URL, and it should be https://html.spec.whatwg.org/multipage/semantics.html#meta-application-name

[aphillips]

The browser accept language is the range. If set to ja-JP that finds either lang=ja or lang=ja-JP before defaulting. IOW it is what you call normal matching.

[r12a]

hmm, yes, i think i read the spec incorrectly.

btw, any idea whether this actually works anywhere? I couldn't find a browser that did anything with it.

[aphillips]

?? Browsers don't do anything with it because servers normally do the content negotiation. (that's not entirely true of course. Webapps sometimes do content negotiation locally.)

[aphillips]

Appears to need a PR from us.