Validation at http://d-theme.com/mulpo against CSS 3 produced the following errors. The first three look like errors worth fixing.

URI : http://d-theme.com/sites/all/themes/mulpo/style.css
302 input.node-add-to-cart Value Error : cursor hand is not a cursor value : hand
337 .view-data-node-data-field-image-cache-field-image-cache-fid Value Error : background only 0 can be a length. You must put a unit after your number : url(images/top-round.gif) no-repeat 0 50
487 .view-tweets Property word-wrap doesn't exist : break-word
552 .node div.file-uploads Property -moz-border-radius doesn't exist : 10px
553 .node div.file-uploads Property -webkit-border-radius doesn't exist : 10px
640 .commenttext Property -moz-border-radius-bottomleft doesn't exist : 10px
641 .commenttext Property -moz-border-radius-bottomright doesn't exist : 10px
642 .commenttext Property -webkit-border-radius doesn't exist : 10px

Validation against the older CSS 2.1 produced the previous errors plus the following error. I know from other themes that last-child is used in menus. I document this for people who might want compatibility with older browsers and validate against older versions of CSS.

URI : http://d-theme.com/sites/all/themes/mulpo/style.css
181 Unknown pseudo-element or pseudo-class :last-child

Comments

ipwa’s picture

ipwa CreditAttribution: ipwa commented

Hi Peter, thanks for checking this theme for me. I will have a look and fix those errors, but as you said I will probably keep webkit & mozilla border-radius until CSS 3 is more widely supported. I have the hand cursor value so that the cursor works in earlier versions of ie doing image replacement on input elements. Will check if this is still needed. Will fix this for the next beta release, thanks!

ipwa’s picture

ipwa CreditAttribution: ipwa commented
Status: Active » Closed (works as designed)

Hi Peter, fixed the other errors and committed to dev. I will leave word-wrap because it is a property that works (http://www.css3.com/css-word-wrap/) as well as -moz and -webkit-border-radius, I don't mind having those validation errors because I know the rest of the code is valid and I'm using those properties for a reason, so I don't want to have to sacrifice the way the theme looks on most browsers, in order it for it to validate. Thanks, marking this as by design, new beta release coming soon when I fix some more issues.