> Having priorities and weight and language lists in the manifest help for negociation, but at the core of it, the user will want to choose language based on co

> Having priorities and weight and language lists in the manifest help for negociation, but at the core of it, the user will want to choose language based on context and content. Yup, agreed. I highly doubt most websites even look at those weights in the Accept-Language header anyways. Having a list of supported langs in the manifest costs nothing. Lazy-load the manifest when the user goes to use the language selection dropdown, or when the response from the server is in a different language than the one requested in Accept-Language (check Content-Language or html `lang` attr). Looks like there's a name for this, but no standard: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Content_negotiation#agent-driven_negotiation https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Con...