Chris Eppstein
Chris Eppstein
I'm pretty sure the [pre-release](https://rubygems.org/gems/fancy-buttons/versions/1.1.0.alpha.1) works. Brandon has been just waiting for the sass release to make that official.
That's a good idea. In the meantime, can you file a bug on compass-rails about the issues you're having and we'll try to get it sorted out.
cc: @nex3
> What CSS classes are generated incorrectly? Please link to the Sass issue so we can investigate.
``` $ irb irb(main):001:0> require 'sass/version' => true irb(main):002:0> Sass::VERSION => "3.4.4 (Selective Steve)" irb(main):003:0> Sass.version => {:major=>3, :minor=>4, :teeny=>4, :name=>"Selective Steve", :date=>#, :number=>"3.4.4", :string=>"3.4.4 (Selective Steve)"} irb(main):004:0> Sass.version[:major] ==...
The solution, clearly, is to only support ``
@wycats but that's not what I saw when I put the exact same syntax in my browser. When I did this as a stand alone HTML file my namespaced CSS...
Hmmm. Maybe my test lacked the doctype. 😅
The postcss-selector-parser api is really weird when it comes to handling raws (escapes, comments, and intervening whitespace). Sometimes comments are their own node, sometimes comments are part of raws, etc....
> Comments must be a separated node. PostCSS also [does not follow this rule][declaration_comment_ast]. I think it's very confusing. There are some comments in "inconvenient locations" that will not be...