- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 15 Jan 2014 15:39:40 +0000
- To: Richard Ishida <ishida@w3.org>
- Cc: Simon Sapin <simon.sapin@exyr.org>, www-style <www-style@w3.org>, WWW International <www-international@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>
On Wed, Jan 15, 2014 at 3:22 PM, Richard Ishida <ishida@w3.org> wrote: > I don't expect that the ordinary user of CSS will see any sophistication > here - for them this is just an @-rule with some special characteristics > that they need to get right if it's going to be effective. Why don't we just > frame it that way in the spec? I think the benefit would be that (a) it's > more straightforward, and (b) that it doesn't make it look like we suck > (instead, those people who don't follow the special rules would just make > pages that suck). The suckage cannot be removed. For compatibility it has to show up in the object model. That's the whole problem. If that was not a requirement we could skip the @charset bytes before parsing and treat @charset rules as errors during parsing. -- http://annevankesteren.nl/
Received on Wednesday, 15 January 2014 15:40:10 UTC