Bug 19236 - Inspector should show CSS warnings/errors
Summary: Inspector should show CSS warnings/errors
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 9687 102750
Blocks:
  Show dependency tree / graph
 
Reported: 2008-05-23 17:41 PDT by Anthony Ricaud
Modified: 2014-01-12 15:02 PST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony Ricaud 2008-05-23 17:41:34 PDT 
Like HTML or JS, CSS problems should be visible. Either in the console and in the resource pane.
Comment 1 Alexander Pavlov (apavlov) 2011-01-01 05:17:39 PST 
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.
Comment 2 Simon Fraser (smfr) 2012-10-01 12:48:44 PDT 
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
Comment 3 BJ Burg 2014-01-12 15:02:52 PST 
CSS errors and warnings are logged to console and highlighted in the CSS text editor in the current inspector.