{"id":363616,"date":"2022-02-28T07:20:29","date_gmt":"2022-02-28T15:20:29","guid":{"rendered":"https:\/\/css-tricks.com\/?post_type=newsletters&p=363616"},"modified":"2022-07-14T16:25:33","modified_gmt":"2022-07-14T23:25:33","slug":"292-a-short-history-of-specificity","status":"publish","type":"newsletters","link":"https:\/\/css-tricks.com\/newsletter\/292-a-short-history-of-specificity\/","title":{"rendered":"292: A Short History of Specificity"},"content":{"rendered":"\n
[Robin]:<\/strong> Sometimes CSS can feel like everyone is shouting\u2026<\/p>\n\n\n\n Ah! Please stop yelling at me!<\/p>\n\n\n\n Whenever I read stuff like this I think ah, yes, you are trying to override some other CSS in some other file that has high specificity and you have resorted to just screaming at the browser in order to fix it.<\/em> It sure works and all, but it\u2019ll lead to problems down the line; fragile code, tech debt, etc.<\/p>\n\n\n\n.overly#powerful .framework.widget {\n color: maroon;\n}<\/code><\/pre>\n\n\n\n