From e5d6c17a1211ecd15568ba9cf8869e921e010dd2 Mon Sep 17 00:00:00 2001 From: Seth Warburton Date: Fri, 28 Nov 2014 13:23:02 +0000 Subject: [PATCH 1/2] Update css.md --- manual/en-US/coding-standards/chapters/css.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/manual/en-US/coding-standards/chapters/css.md b/manual/en-US/coding-standards/chapters/css.md index 91979236..b0d0fe57 100644 --- a/manual/en-US/coding-standards/chapters/css.md +++ b/manual/en-US/coding-standards/chapters/css.md @@ -53,7 +53,12 @@ Subsections should be normally cased and within an open comment block. // These are stripped on compile. ``` -## Class naming +## CSS selectors +Only use classes for CSS selectors, *never IDs* as they intoduce unwated speficity to the cascade. It takes 255 chained css class selectors to override a single ID, so using an ID as a css selector is like firing the first nuke; you begin a specifity war that can only escalate, with terrible consequence. + +To put it another way; Don't use a Sith Lord when just two Storm Troopers will suffice: [CSS Specifity Wars](http://www.stuffandnonsense.co.uk/archives/css_specificity_wars.html) + +### Class naming convention Use dashes to create compound class names: ```css From da6f54df75c4c0c2228c638f86aabffd5ccb6274 Mon Sep 17 00:00:00 2001 From: Seth Warburton Date: Fri, 28 Nov 2014 16:54:46 +0000 Subject: [PATCH 2/2] Update css.md --- manual/en-US/coding-standards/chapters/css.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manual/en-US/coding-standards/chapters/css.md b/manual/en-US/coding-standards/chapters/css.md index b0d0fe57..b4a8c2bc 100644 --- a/manual/en-US/coding-standards/chapters/css.md +++ b/manual/en-US/coding-standards/chapters/css.md @@ -54,9 +54,9 @@ Subsections should be normally cased and within an open comment block. ``` ## CSS selectors -Only use classes for CSS selectors, *never IDs* as they intoduce unwated speficity to the cascade. It takes 255 chained css class selectors to override a single ID, so using an ID as a css selector is like firing the first nuke; you begin a specifity war that can only escalate, with terrible consequence. +Only use classes for CSS selectors, *never IDs* as they introduce unwanted specificity to the cascade. Using an ID as a css selector is like firing the first nuke; you begin a specifity war that can only escalate, with terrible consequence. -To put it another way; Don't use a Sith Lord when just two Storm Troopers will suffice: [CSS Specifity Wars](http://www.stuffandnonsense.co.uk/archives/css_specificity_wars.html) +To put it another way; Don't use a Sith Lord when just two Storm Troopers will suffice: [CSS Specificity Wars](http://www.stuffandnonsense.co.uk/archives/css_specificity_wars.html) ### Class naming convention Use dashes to create compound class names: