19236 2008-05-23 17:41:34 -0700 Inspector should show CSS warnings/errors 2014-01-12 15:02:52 -0800 1 1 1 Unclassified WebKit Web Inspector (Deprecated) 528+ (Nightly build) All All RESOLVED FIXED P2 Normal --- 9687 102750 1 rik webkit-unassigned apavlov aroben bburg priyajeet.hora simon.fraser oldest_to_newest 81371 0 rik 2008-05-23 17:41:34 -0700 Like HTML or JS, CSS problems should be visible. Either in the console and in the resource pane. 328271 1 apavlov 2011-01-01 05:17:39 -0800 What constitutes a CSS warning/error? The CSS spec is quite liberal to the CSS stylesheet format: http://www.w3.org/TR/CSS21/syndata.html#parsing-errors. Thus, it is debatable which violations should actually count as errors. 731913 2 simon.fraser 2012-10-01 12:48:44 -0700 There are various useful things we could display: 1. Parsing errors; highlighting syntax errors like missing braces or semicolons 2. Content errors: invalid properties (though we probably don't want to show all these, since people make use of this in valid stylesheets) invalid values 3. Improvement suggestions: e.g. large negative text-indent not coupled with overflow:hidden 967043 3 bburg 2014-01-12 15:02:52 -0800 CSS errors and warnings are logged to console and highlighted in the CSS text editor in the current inspector.