Re: Issues arising from not reparsing

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.   `._.-(,_..'--(,_..'`-.;.'