We use industry standard minifier scripts to make the CSS files as small and efficient as possible. It might be the case that they don't generate 100% valid output but they generate output that is understood by all browsers. However in this case, some of the errors shown don't make sense to me and look more like the validation script is getting confused.

OK Thanks, will see what I can find

/rsc/build/b2evo_base.bmin.css

Working from bottom up of the 22 errors,

1. 110% is not a valid letter spacing, I find it should only be a pixel value
http://www.w3schools.com/cssref/pr_text_letter-spacing.asp though {em} works too http://www.w3schools.com/cssref/tryit.asp?filename=trycss_js_letter-spacing



Another find https://www.hscripts.com/tutorials/css/letter-spacing.php but no % option




So I've changed 110% to 0.1em




---



2. Corrected .btn-default:hover{color:333; by adding hash before number :)

---



3. @-moz-document url-prefix(){.notes a.roundbutton{top:0}} This seems pointless so have modified it to .notes a.roundbutton{top:0} in case there's some use for that bit.

---

Ok I have the errors down to 9 by adding tilda ~ before the progid:DXImageTransform ~progid:DXImageTransform
This removes two of the three errors for each instance.
OK Changed
filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#a0a0a0', endColorstr='#d2d2d2')
to
-ms-filter: "progid:DXImageTransform.Microsoft.gradient(startColorstr='#a0a0a0', endColorstr='#d2d2d2')"
prepending with-ms- and surrounding progid:DXImageTransform.Microsoft.gradient(startColorstr='#a0a0a0', endColorstr='#d2d2d2') with quotes removes all errors of this type (single or double quotyes seem to work)
Also seems ok to remove quotes around colour values

I've split the code into lines to better see where the errors are: I only have 4 errors now:
http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fcalstock.org.uk%2Felf.php

This accounts for three of them, this is the code without the three error messages
a.rollover_sprite:hover span.icon{visibility:hidden;visibility:visible\0/}@media screen and (min-width:0\0){a.rollover_sprite:hover span.icon{visibility:visible}}

and one more, this is the error message
unrecognized media \000000screen \0screen{#styled_contentblock span[class*=status] span,.evo_contentblock span[class*=status] span{top:-15px;left:-2px}}

UPDATE: Separated the above so problem lies only in first line below
@media \0screen{#styled_content_block span[class*=status_] span{top:-15px;left:-2px}}
.evo_content_block span[class*=status_] span{top:-15px;left:-2px}

Ok, we'll have a deeper look.

is the \0 just for IE 8? If so I may just cut it out

Have commented out the offending parts until I find either a solution or a valid use for them.

/*a.rollover_sprite:hover span.icon{visibility:hidden;visibility:visible\0/}@media screen and (min-width:0\0){a.rollover_sprite:hover span.icon{visibility:visible}}*/
and
/*@media \0screen{#styled_content_block span[class*=status_] span{top:-15px;left:-2px}}*/

Some of these issues were fixed here:

• https://github.com/b2evolution/b2evolution/commit/efb76d5db2b4d8b7e3d9296f5279b77d07a94e84
• https://github.com/b2evolution/b2evolution/commit/db86b08da74c93efeaea60b3fff5f888e9927a60

This will be part of release 6.7.5

@fplanque wrote earlier:

Some of these issues were fixed here:

• https://github.com/b2evolution/b2evolution/commit/efb76d5db2b4d8b7e3d9296f5279b77d07a94e84
• https://github.com/b2evolution/b2evolution/commit/db86b08da74c93efeaea60b3fff5f888e9927a60

This will be part of release 6.7.5

They were HTML5 validation errors not the CSS ones :)
http://forums.b2evolution.net/html5-validation-of-6-7-4

but nice that they'll be in the next release.

Ah sorry wrong topic. So I reposted on the other one and this one is still open.