sc_bootstrap.css CSS-Validator

There's not much that can be done to 'fix' it right now. The CSS works in all major browsers and is mostly what's provided directly by the Twitter Bootstrap group.

With that said, we have plans to overhaul our layout and CSS system over the next few releases. The mammoth file we're using is hard to maintain and edit for our users.

Of course if you're seeing any functional issues with our file, just let us know. Most validation issues are not known to cause any problems with browsers and Google has stated that validation issues do not affect your rankings in any way.

I hope that helps,
Alex

Alex,
Thanks for the tip. I've added it to our tracker to investigate for the next release in February.

Honestly, we're always trying very hard to improve our validation wherever we can. It's really not something that search engines or most/any browsers actually care about.. but we know that many users (and their clients) demand validation. If we can update that namespace string, which from a *very* quick investigation, it does seem like your solution is viable and recommended from the few places I've seen. I'm not sure when Facebook updated that syntax, but we'll get on it.

With luck, this update should be in the release in a few weeks.

Thanks,
Alex

Just wanted to update this post and let you know that we'll be implementing the new prefix= setting for the namespaces that we include. That will be in the next release, due out around mid/late February.

From our investigation, it's definitely valid syntax. We also tested with validator.w3.org and it removes a few issues that are shown there.

Thanks for the tip!
Alex