-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partial handling of "background-image" property #6
Comments
Well, initially the goal was to cover both |
To elaborate: the problem is that you'd need to emit additional CSS syntax, not just modify existing. While possible, it's a different beast. You'll see what I mean if you look at the replacing code, https://github.com/yostudios/Spritemapper/blob/master/spritecss/replacer.py#L27 |
Ok, I see what you mean : the CSS modifications seem to be simple "search/replace" on Unfortunately, I'm not a python coder, therefore I can't even try to fix it myself... Thanks for your answer ! |
I'm having trouble getting sitemapper to work at all.
I get a As mentioned here, if I separate the background properties into background-color, background-image, etc, sitemapper doesn't handle it. In an attempt to get something out, I tried simply:
on a couple rules, and I get the error
I believe spritecss.png is the sprite image file you are creating. |
Spritemapper only handles No, Edit: The reason your first declaration doesn't work is that it specifies background positions; these are probably not sprites. |
SpriteMapper successfully detects the pictures in "background-image" CSS properties and adds them in the spritesheet, but it "forgets" to handle the "background-image" in the resulting CSS file : they are not updated to target the spritesheet PNG file, and no "background-position" is set.
The "background" properties in the same file are OK, though...
A solution could be replacing "background-image: " with "background :" in the CSS file ; but they are some cases where you really need to use "background-image " instead of "background".
The text was updated successfully, but these errors were encountered: