W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [cssom] Rationale for including (or not) CSSCharsetRule

From: Simon Sapin <simon.sapin@exyr.org>
Date: Tue, 28 May 2013 22:24:13 +0800
Message-ID: <51A4BE0D.60009@exyr.org>
To: Simon Pieters <simonp@opera.com>
CC: "www-style@w3.org" <www-style@w3.org>, Glenn Adams <glenn@skynav.com>, Anne van Kesteren <annevk@annevk.nl>
Le 28/05/2013 21:21, Simon Pieters a écrit :
> Hi Glenn and Anne
> In
> http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Attic/Overview.html?rev=1.166;content-type=text%2Fhtml#history
> CSSCharsetRule was obsoleted because it was "not deemed necessary".
> In https://dvcs.w3.org/hg/csswg/rev/961ed47ad0fc it was restored by Glenn.
> I could not find any discussion about either of these decisions. If I
> missed it, please provide a pointer.
> Could both of you please elaborate on the rationale regarding
> CSSCharsetRule?
> If anyone else has opinions about CSSCharsetRule, please state them.

@charset is not a rule comparable to @import, it’s closer to a BOM. It’s 
not something defined in terms of component values, tokens, or even 
characters, it’s an exact byte pattern that is matched before 
tokenization even starts.

What would it mean to add or change a CSSCharsetRule on a parsed stylesheet?

Simon Sapin
Received on Tuesday, 28 May 2013 14:24:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:30 UTC