Valid XHTML and CSS

Topics: General
Jan 26, 2011 at 7:41 PM

C1 website states: Valid XHTML and CSS

Checking XHTML via http://validator.w3.org/#validate_by_uri+with_options I can confirm this for XHTML.

Checking CSS via http://jigsaw.w3.org/css-validator/#validate_by_uri+with_options it gives > 80 errors and > 250 warnings.

So what's up with CSS validity?

 

Developer
Jan 26, 2011 at 9:01 PM
Edited Jan 26, 2011 at 9:14 PM

I may sound meticulous (sorry!) but have only found a mention of "XHTML validation" :) - http://www.composite.net/C1/Intro/Features.aspx

Of course, CSS validation might be something to improve about C1. A good point.

Coordinator
Jan 26, 2011 at 9:22 PM

@microfox You are absolutely right - on our *own* websites we have a text in the footer claiming that our site is is 'valid xhtml and css' - our pages are valid xhtml, but when doing our layout a lot of css hacks were used used (like .htc files to get rounded corners in IE7+, chrome/mozilla specific css for the same effect etc.). These items a fairly common tricks of the trade, but not valid w3c css.

We will remove the 'valid CSS' claim - we need the css hacks on our site to ensure that it looks as it does.

Just to ensure there is no confusion: Composite C1 will output what you put into it - if you write CSS or HTML that does not validate, then that is what you get (the exception here is our visual editor's code editor which will keep bitching until you write valid xhtml) . By default we ship layouts / packages that we strive to keep simple and valid. The issue here is our own website, not the ability of the CMS to conform to w3c rules.

 

Coordinator
Jan 26, 2011 at 9:27 PM

There - now we just claim to send you valid xhtml on our 4 websites. Thanks for pointing this out!

Jan 26, 2011 at 10:59 PM

Thanks for clarification.