Closed ericpedia closed 12 years ago
The first thing I always do with things like this is check issues from the original repo, sometimes helps save time.
Right, I didn't find it there; should I assume any SASS-to-CSS output issue is a PHPSASS issue and not WPSASS?
On Aug 30, 2012, at 2:56 PM, Noel Tock wrote:
The first thing I always do with things like this is check issues from the original repo, sometimes helps save time.
? Reply to this email directly or view it on GitHub.
This might be the issue (or part of it)?
I think so yeah. Wp-sass is just a Wordpress wrapper for that package so if there's a problem with wp bugs or plugin/theme conflicts etc... let me know :)
FYI the relevant PHPSass issue is this one: https://github.com/richthegeek/phpsass/issues/45
Not sure if this is a phpsass issue or a wp-sass issue (or if I'm somehow misapplying \@extend):
SCSS:
Resulting CSS:
Note that the :before and :after properties is getting added not to
.myclass ul li:before
and.myclass ul li:after
, but directly to.myclass ul li
.