-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Respond doesn't work with -sass-debug-info in CSS? #274
Comments
+1 |
Same issue as #148 but closed unfixed? |
Yeah, you'll need to remove commented-out media queries from your CSS for respond to work. The parser is pretty simple and works with any mqs it finds. On May 27, 2014, at 10:22 AM, Chris Wilson [email protected] wrote:
|
This case is about using media queries for Sass' debug-info blocks. Looking closer, this issue stems from the fact that nested media queries are not supported -- since the debug-info queries are added inside of the real media query blocks. |
+1 In case anyone ends up here from the same Drupal aggregated CSS nightmare I just came from, here's a relevant thread: https://drupal.org/node/1995938 |
Just discovered that my app's media queries don't respond on IE8. Respond.js seems to find a large number of media queries, and almost all of them are SASS debug info. See the attached file for example, which works in most browsers but not in IE8 with respond.js (for me).
It never seems to interpret the real media queries in that file. If I disable the debug info then it works in respond.js. Tried both 1.4.2 and current HEAD of respond.js, same results.
Is it possible that it doesn't like something about the debug info?
https://gist.github.com/qris/11291896
The text was updated successfully, but these errors were encountered: