Would You Consider These Big CSS Errors In Validation

Discussion in 'CSS' started by phaze3131, Apr 9, 2009.

  1. #1
    phaze3131, Apr 9, 2009 IP
  2. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #2
    What's preventing CSS validation is the opacity declarations - and those are browser specific and not valid CSS, but entirely harmless... It's just another of the reasons valid CSS is pretty much a joke if you care about all browsers.

    I don't sweat invalid CSS when I know WHY it's invalid and WHY I'm using the invalid properties. zoom:1; -moz properties, expressions, filter - I know WHY I'm using them, so I don't worry about them throwing errors in the validator.

    Though you may want to reverse the order of those opacity declarations - opacity, then -moz-opacity, then filter. I've had Safari ignore the opacity declaration if the other two are first (though they fixed it in Safari 3, better safe than sorry)

    Likewise, it's bad practice to start a number with a decimal point. Put that zero in there.

    I'd be more concerned about your 17 validation errors on your markup, excessive unneccessary classes and DIV, presentational markup, etc, etc...
     
    deathshadow, Apr 10, 2009 IP