mwrock/RequestReduce — Issue #76: Resolve CSS Inheritance (specificity) rules in spriting process
Author: mwrock
Created: 2011-11-20 16:02:37+00:00
State: open

Currently alot of background images are not sprited because of RequestReduce's limitation to treating each css class as an atomic unit. Inheritable dimensions and padding is lost which either makes an image unspritable by RR or the sprite is malformed because of improperly calculated dimensions.

Further, pre-sprited images in a document about to be reduced are often malformed and rendered in a distorted fashion because it is common practice to place the background url in one widely inherited class and have more specific classes define just the background-position. This makes many initial renderings using RequestReduce give a bad first impression especially if the user does not read the wiki on preparing the sprites and spriting requirements. It can also make the exercise of converting docs to be compatible with RR spriting, a time consuming and tedious endeavor.

I had initially thought this was a small edge case but it is proving to be an all too common problem and I think the adoption story could be dramatically improved by adding this feature.

Unfortunately it is not a small effort.