Language tag handling #2
Description
This issue is for discussing the questions noted in the explainer around language tag handling. As noted there, we're not quite sure what the right path is here. Investigating what other APIs do would be helpful.
One issue to worry about here which is more unique to the web is the impact on interop. For example, if a popular implementation supports the nuances of both en-US and en-GB, it might return both as supported. But then, some sites might start relying on this, and locking out browsers which only return en, or only return en-US. This could lead to unfortunate outcomes like browsers starting to lie and say that they support a large set of variants, when in actuality they use the same translation model for all such variants.