New Rule: Selector Validity

[benthemonkey]

(Should the name be valid-selector? selector-validity? no-invalid-selectors?)

This rule checks that all selectors (classes, IDs, etc) adhere to the W3 spec for valid css identifiers

See #327 for a discussion about adding this rule.

[BPScott]

I'll vote for no-invalid-selectors, the convention seems to be no-disallowed-thing, for instance there is already a no-invalid-hex.

[Snugug]

no-disallowed-thing

On Oct 18, 2015, at 2:34 PM, Ben Scott [email protected] wrote:

I'll vote for no-invalid-selectors, the convention seems to be no-disallowed-thing, for instance there is already a no-invalid-hex.

—
Reply to this email directly or view it on GitHub.

[Snugug]

HTML5 is HTML, spec to that, and have an option to "degrade" to HTML4

On Nov 14, 2015, at 8:47 PM, Ben Rothman [email protected] wrote:

According to my brief research, IDs have different constraints in HTML4 vs HTML5. Should I include an option here to specify the spec? I'm leaning toward the rule simply testing adherence to HTML4, as my general use case is writing code to test with latest Chrome, only to run into subtle problems with IE8. Also constraints on IDs are pretty lax with HTML5.

—
Reply to this email directly or view it on GitHub.