- From: Chris Lilley via GitHub <noreply@w3.org>
- Date: Sun, 01 Jun 2025 16:54:51 +0000
- To: public-css-archive@w3.org
> Can we get some better interop here? Ideally, I think we should agree (and perhaps clarify in a note somewhere) that _only_ well-formed BCP 47 language tags will have any effect on the content-language-dependent CSS features, and the browsers that are currently accepting ill-formed tags should stop doing so. > > Alternatively, we should agree exactly what kinds of ill-formed tags _are_ accepted, and record this in a spec so that we can all converge on compatible behavior. It makes no sense that `en_US` enables US English hyphenation in Chrome on macOS but not in Chrome on Windows; and it makes no sense that `de_AT` selects Austrian-German hyphenation but does _not_ activate Austrian-German quote marks. How widespread is the use of underscore in language tags? I agree that we should have platform- and browser- consistent behavior, but is it worthwhile to update BCP47 to accept underscore identically to hyphen? Perhaps as a deprecated alias? -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7098#issuecomment-2927528604 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 1 June 2025 16:54:51 UTC