Comments on: The Big CSS3 Validation Debate

By: Graeme

Graeme — Fri, 21 Oct 2011 23:37:42 +0000

I agree with all of the comments above, and will add that it seems as if W3C is waiting for Microsoft to come on board before bringing the CSS3 validation standard up to date.

For years now I’ve been reading about how vendor-specific CSS3 code fails validation, but the W3C tutorial on browser support describes the use of vendor-specific properties. It seems pointless not treating them as valid CSS3 when W3C has specified how to implement them.

I also support the idea of flagging unsupported properties as ‘experimental’.

By: robin

robin — Wed, 05 Oct 2011 13:58:47 +0000

I personally love CSS3 and strongly think that W3C needs to get in the swing of things and do something now. I mean come on there are lots of good solutions around making it so that the code dose not come up as an error so I say it’s time W3C picks one of the many solutions and implements one because site designers are getting feed up with W3C being out of date.

By: HTML5 & CSS3 draws fans and skeptics alike « nickpolo85

HTML5 & CSS3 draws fans and skeptics alike « nickpolo85 — Tue, 30 Aug 2011 03:17:42 +0000

[...] Helpful link 1: http://www.css3.info/the-big-css3-validation-debate/ [...]

By: Lee Mason

Lee Mason — Wed, 20 Jul 2011 13:22:12 +0000

The best solution would be for the browser vendors to make browsers that utilise W3 standards (i’m dreaming i know).

But short of that +1 for giving the option on the validator to ignore browser specific declarations.

It might just be me but i pride myself on being able to add a little “website validated with no errors” icons to show the site is valid and well developed.

But recently ive only been able to do this for the html.

Yes “technically” its not valid with these specific declarations but in the real world my CSS is valid and web designers that achieve this should be able to state it.

By: mmw

mmw — Thu, 14 Jul 2011 02:24:16 +0000

ha sorry, no test for html tag inputs clap clap to the owner of this blog…

link rel=”stylesheet” type=”text/css” href=”resources/editing.css” /
link rel=”stylesheet” type=”text/css” href=”resources/editing-vendor-specific.css” /

By: mmw

mmw — Thu, 14 Jul 2011 02:22:40 +0000

I might sound like weirdos but I am doing that since a decade… in vendor specific your overload your class and id whatever, think different don’t be a fake…, when you poooooo you swap your ass?, coding that’s the same.

By: Rico

Rico — Mon, 28 Feb 2011 17:19:33 +0000

Sorry Andrew, but…

“Sorry! We found the following errors (3)
URI : http://www.osinova.co.uk/
82 .main Property -moz-border-radius doesn’t exist : 10px 10px
83 .main Property -webkit-border-radius doesn’t exist : 10px 10px
84 .main Property border-radius doesn’t exist in CSS level 2.1 but exists in : 10px 10px”

the same is for CSS3 validation 8o)

By: Andrew Osiname

Andrew Osiname — Fri, 07 Jan 2011 22:16:06 +0000

Heres a nice little hack:

Visit http://www.osinova.co.uk and note that border radius is used
Now click the css validator and you see it passes

Heres how to do it:

.main {

-moz-border-radius:10px;
-webkit-border-radius:10px;
border-radius:10px;

border: 15px solid #222222;
margin:auto;
background:#FFF;
width:760px;
}

By: Gareth Parkinson

Gareth Parkinson — Thu, 21 Oct 2010 09:21:33 +0000

I strongly agree with the need for Validation and am pretty anal when it comes to making sure something is valid.

But in todays market, clients always want something that looks different from everyone else, and want to stand out from the crowd.

CSS3 offers this, but the validator for W3C is not allowing designers to use it without the errors. The requirement for validation is strong, and I feel that a site is incomplete if it doesn’t pass W3C validation.

The fault isn’t that designers are using “Experimental Code”, the fault is that W3C are so bloody indecisive about what standards they want to keep and which ones they want to remove. CSS3 has been in development for a good while now, which is why the majority of browsers support similar standards.

W3C need to change the errors into Experimental Tags. It is upto the designer to explain to their client that the styling uses CSS3 and it is their job to also ensure that the website remains compliant and functional.

This is an easy fix if the website is displaying links to the validators from the individual pages.

W3C need to adjust the validator, not designers ceasing to use CSS3. CSS3 gives us more beautiful websites, which we need on the web.

By: Marsha

Marsha — Sat, 25 Sep 2010 12:04:44 +0000

At the same time, I have to question whether or not the time has yet come for designers to be implementing CSS3 in their client projects. I think CSS3 is perfectly acceptable to be used in a designer’s own projects, and quite essential to promote the growth of CSS3, but is it really acceptable to sell a client experimental code that could cease to function at any time if the W3C ammends a specification, or browser vendors change the syntax with which a property is implemented?

Agreed. I removed CSS3 from my current project after reading this.