- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Jan 2017 23:48:29 +0000
- To: public-css-archive@w3.org
dbaron has just created a new issue for https://github.com/w3c/csswg-drafts: == [css2-testing] encoding detection doesn't match level 3 or WG's resolution == The [changes section of css2-testing](https://drafts.csswg.org/css2-testing/changes.html) (or [its equivalent on the CSS2.2 WD on TR](https://www.w3.org/TR/2016/WD-CSS22-20160412/changes.html)) has an [edit to section 4.4 dated 2013-05-02](https://drafts.csswg.org/css2-testing/changes.html#s.4.4). I believe text following this edit still doesn't match the level 3 specification or the [resolution in the minutes that the edit links to](https://lists.w3.org/Archives/Public/www-style/2012Oct/0727.html), and I believe they should match. In particular, [syntax level 3](https://drafts.csswg.org/css-syntax/#input-byte-stream) and the [section of Encoding that it links to](https://encoding.spec.whatwg.org/#decode) (and the Gecko implementation) prioritizes the BOM over *any* information from HTTP or from an at-charset rule. The [current text in CSS 2.2](https://drafts.csswg.org/css2-testing/syndata.html#charset) has the BOM override only when the HTTP specified encoding is one of the UTF* encodings. This disagrees with the [linked resolution](https://lists.w3.org/Archives/Public/www-style/2012Oct/0727.html): > RESOLVED: BOM takes precedence over HTTP. Errata CSS2.1, edit css3-syntax to fix this. /cc @annevk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/992 using your GitHub account
Received on Monday, 30 January 2017 23:48:36 UTC