The nested comment issue is fixed in trunk but I did not try revalidate.
On Oct 9, 7:22 pm, Jonathan Lundell <[email protected]> wrote: > On Oct 9, 2011, at 4:29 PM, pbreit wrote: > > > Advice to beginners: don't get too hung up on stuff like that. > > Us geezers, on the other hand, worry about it, because even when it's > harmless the noise obscures real errors. In the case of the welcome app, > there's a real error: > > <!--[if IE]> > <!-- Always force latest IE rendering engine > (even in intranet) & Chrome Frame > Remove this if you use the .htaccess --> > <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> > <![endif]--> > > HTML comments do not nest. The effect of the code above (which the w3 > validator objects to) is that *all* browsers see the meta element (and the > endif, for that matter) that are intended only for IE. It should be: > > <!-- Always force latest IE rendering engine > (even in intranet) & Chrome Frame > Remove this if you use the .htaccess --> > <!--[if IE]> > <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> > <![endif]--> > > ...though I don't really understand the "if you use the .htaccess" comment. > > The validator also objects to this, because there's no 'copyright' name > defined for meta: > > <meta name="copyright" content="Copyright 2011" /> > > Notice that even if a copyright name were defined, this one is meaningless, > since it neglects to tell us who owns the copyright.
