Vae doesn't like HTML5Boilerplate?
  • I currently am using

    I believe a lot of the CSS doesn't validate because it uses a few hacks to maximize usability. I'm not sure if this is causing parsing errors with vae... but when I use v:asset, it's removing random parts from my CSS file.

    For example, it's removing font-weight:bold from my headings, and it's removing some of my @font-face font-families (but not others).

    It's very weird, I can only imagine it's because it's parsing the CSS sheet wrong because it's not 'valid' in the first place.

  • 2 Answers sorted by
  • Hey Travis,

    Yep this is because we, by default, will attempt to minify your CSS assets. You can disable this behavior (which will make your CSS work) by going to the Site tab > Optimization and checking the checkbox labelled "Disable CSS Asset Minification".

    Hope that helps!

  • Perhaps you could look into finding a new CSS minifier? Right now v:asset messes up a lot of cross-browser CSS instructions. E.g:

        background-image: -webkit-gradient(linear, left top, left bottom, from(#a0cfeb), to(#00a1de));
    background-image: -webkit-linear-gradient(top, #a0cfeb, #00a1de);
    background-image: -moz-linear-gradient(top, #a0cfeb, #00a1de);
    background-image: -ms-linear-gradient(top, #a0cfeb, #00a1de);
    background-image: -o-linear-gradient(top, #a0cfeb, #00a1de);
    background-image: linear-gradient(top, #a0cfeb, #00a1de);

    Will result in only the first statement being preserved.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

In this Discussion