CSS numbers without units where units are necessary should cause a warning

[kevinbarabash]

In this case top and left should have units after their values.

#greeting { 
background: rgb(255, 255, 0); 
border: 2px solid black; 
font-family: "Comic Sans MS", fantasy; 
padding: 5px; 
width: 262px; 
position: absolute; 
top: 100; 
left: 20; 
z-index: 2; 
} 

[pamelafox]

I think causing a gutter warning is fine/helpful - Chrome does that sort of thing in the dev tools ("invalid property value") - but an error seems too aggressive in this case.

[kevinbarabash]

@pamelafox sounds good.

[jjwon0]

seems there'd be append a lot of information to slowparse to make it validate css. right now, slowparse is more structural.

we could consider integrating csslint into live-editor as well.