- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Apr 2020 15:38:29 +0000
- To: public-css-archive@w3.org
fwiw, reasons HTTP language declarations are problematic include: - they represent metadata rather than language-processing language - they may have multiple language value arguments, which is not appropriate for applying language for language-processing, and which currently breaks language declarations for browsers - HTTP declarations don't work unless the resource is served by a server - it suggests to authors that it may be ok to use the Content-Language meta element, which is deprecated in HTML and doesn't actually work on all browsers -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5031#issuecomment-621932681 using your GitHub account
Received on Thursday, 30 April 2020 15:38:31 UTC