Summary: | Inspector should show CSS warnings/errors | ||
---|---|---|---|
Product: | WebKit | Reporter: | Anthony Ricaud <rik> |
Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | apavlov, aroben, bburg, priyajeet.hora, simon.fraser |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 9687, 102750 | ||
Bug Blocks: |
Description
Anthony Ricaud
2008-05-23 17:41:34 PDT
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. 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 CSS errors and warnings are logged to console and highlighted in the CSS text editor in the current inspector. |