W3C home > Mailing lists > Public > public-html@w3.org > October 2009

Re: Issues arising from not reparsing

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 27 Oct 2009 06:25:00 +0000 (UTC)
To: Simon Pieters <simonp@opera.com>
Cc: HTMLWG WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0910270538030.9145@hixie.dreamhostps.com>
On Mon, 26 Oct 2009, Simon Pieters wrote:
> On Mon, 26 Oct 2009 01:59:49 +0200, Ian Hickson <ian@hixie.ch> wrote:
> > > 
> > > It would be good to have similar (but less complex) content model 
> > > restrictions on the other (r)cdata elements in order to make 
> > > <style><!--</style> invalid because that causes weird parsing in 
> > > legacy browsers and is clearly an authoring mistake.
> > 
> > What rule do you want? Just making "<!--" invalid?
> 
> I think that would be annoying for people who have 
> <style><!--...--></style> today. I think I want the rule to be that 
> elements not end with an open escape.

On Mon, 26 Oct 2009, Simon Pieters wrote:
>
> I think you're both missing the point. The strings <!-- and --> are 
> still passed to the CSS parser.
> 
> What's being discussed is making validators whine about 
> <style><!--...</style>, because that causes weird parsing in legacy 
> browsers. (It could also be something like <style> *[foo="<!--"] { ... } 
> </style> or <style> /* <!-- woot --!> */ </style>.)

Ok, done.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 27 October 2009 06:25:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:09 UTC