4 ms·

Some details would be nice.

• config_yml 15y ago
  Well, multiple editors were at work. The approach described creates selectors that were generally more specific than they needed to be. Eventually, people needed something to be styled differently in a context that was already heavily specified. So they needed to have even more specific selectors to override an existing selector. As soon as someone stuck some ID in front of that whole selector (which is almost too easy using SASS/SCSS) it was basically game over. I think OOCSS is an approach to help here, but once you have such a mess it is pretty hard to refactor.
  • rimantas 15y ago
    God, when this OOCSS thing will be forgoten. It just moves mess to another place and instead of mess in CSS you get mess in CSS and HTML.
    • config_yml 15y ago
      I guess you can create a mess either way. For me OOCSS was easy to scale out onto lots of elements and it was certainly easier to keep track of what is affecting what once you change something.