- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Nov 2014 23:50:18 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27422 --- Comment #3 from Simon Pieters <simonp@opera.com> --- http://dev.w3.org/csswg/css-syntax/#charset-rule explains a bit why it doesn't make sense to have it in the object model. Also see http://www.w3.org/mid/op.wxt85uaqidj3kv@simons-macbook-pro.local * @charset is a syntax construct that should not be part of the object model, much like the BOM and comments are not part of the object model. * When parsing a stylesheet, the first few bytes are scanned for a specific byte pattern to select an encoding. When the actual CSS parser comes to the @charset rule, it is parsed with normal @-rule syntax rules, which is laxer than the scanner. Thus the object model can be claiming an encoding that was not actually picked up by the @charset scanner. * CSSCharsetRule can be modified but that does not change the encoding of the stylesheet. * CSSCharsetRule complicates other parts of CSSOM e.g. insertRule, removeRule, CSSNamespaceRule. I've marked it as being considered for removal in the spec: https://dvcs.w3.org/hg/csswg/rev/86a5f6f5df18 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 25 November 2014 23:50:19 UTC