3 ms·
My examples must be misleading, I'm not against creating classes. All I'm trying to say, is that in some cases (i.e. when you only need a particular set of sty
by analyst74 13y ago
My examples must be misleading, I'm not against creating classes.
All I'm trying to say, is that in some cases (i.e. when you only need a particular set of styles for a single page/section), limiting the scope of those style definition can help dealing with specificity hell / bleeding styles, and make the application more maintainable.
Obviously, this is a trade-off, a big one if you want your site to be consistent across pages. But there will be occasions where one or more page of a site/app is vastly different from other pages.
- Jormundir 13y agoSelecting element types rather than creating new classes is what causes bleeding styles.
- protonfish 13y agoUntil you get class-name collisions or your classes are applied to elements by other developers without you knowing. So you create more unique classes and every element ends up having 12 classes applied to it. Classes are no solution to bleeding styles.