Thread: W3C css Validator problem?
View Single Post
Old 02-27-2013, 07:39 PM   #9
st_albert
Guru
st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'
 
Posts: 698
Karma: 150000
Join Date: Feb 2010
Device: none
I would vote for css 3. I like it to check for typos and syntax errors in my @font-face declarations as well as the rest of the code. (I'm much less likely to try using an unsupported feature than to make a typo!)

Just my $0.02

Albert
st_albert is offline   Reply With Quote