W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2017

[csswg-drafts] [css2-testing] encoding detection doesn't match level 3 or WG's resolution

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
Message-ID: <issues.opened-204165091-1485820107-sysbot+gh@w3.org>
dbaron has just created a new issue for 

== [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 

I believe text following this edit still doesn't match the level 3 
specification or the [resolution in the minutes that the edit links 
 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 
> 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 
Received on Monday, 30 January 2017 23:48:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:07 UTC