This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20787 - vendor-prefixed pseudo-element/pseudo-class should cause Warnings instead of Errors by default
Summary: vendor-prefixed pseudo-element/pseudo-class should cause Warnings instead of ...
Status: RESOLVED FIXED
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: CSS 3 (show other bugs)
Version: CSS Validator
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL: https://twitter.com/necolas/status/29...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-27 12:22 UTC by Michael[tm] Smith
Modified: 2013-02-13 15:05 UTC (History)
2 users (show)

See Also:

Attachments

Description Michael[tm] Smith 2013-01-27 12:22:58 UTC 
see https://twitter.com/necolas/status/295370972326940674

[[Email. Every. Single. Day. "Dear Nicolas, normalize.css does not pass W3C CSS validation. Please fix this."]]

The validator emits several "Unknown pseudo-element or pseudo-class" errors normalize.css and several "unknown vendor extension" for some vendor-prefixed properties.

So it seems like the current default is to report warnings instead of errors for vendor-prefixed properties.

I suggest making that also be the default behavior for vendor-prefixed pseudo-elements and pseudo-classes; that is, report warnings by default for those too, instead of errors.
Comment 1 Yves Lafon 2013-02-13 15:05:47 UTC 
Fixed, sorry for the lack of daily emails as a result of that fix ;)