4 ms·

I'm not sure I understand why precompiling CSS mixins and inheritance are a good idea. If you can define multiple classes for an element (which can override eac

I'm not sure I understand why precompiling CSS mixins and inheritance are a good idea. If you can define multiple classes for an element (which can override each other), why bother?

oscarduignan 16y ago
Chris Eppstein (develops compass) does a great job breaking down the why (for tools like sass in general) here => http://chriseppstein.github.com/blog/2009/09/20/why-stylesheet-abstraction-matters/ http://chriseppstein.github.com/blog/2009/09/20/why-styleshe...
chriseppstein 16y ago
The problem of applying multiple classes to an element arises when the definition of one class expects another css class to be applied to all the same elements because there is an implicit inheritance relationship between them. Keeping inheritance in the stylesheet allows the implementation details of those classes to be kept together instead of leaking out to the html and causing display bugs (which are very hard to unit test).