Skip to content
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

Open
qris opened this issue Apr 25, 2014 · 5 comments
Open

Respond doesn't work with -sass-debug-info in CSS? #274

qris opened this issue Apr 25, 2014 · 5 comments

Comments

@qris
Copy link

qris commented Apr 25, 2014

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

@nwhittaker
Copy link

+1

@qris
Copy link
Author

qris commented May 27, 2014

Same issue as #148 but closed unfixed?

@scottjehl
Copy link
Owner

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:

Same issue as #148 but closed unfixed?


Reply to this email directly or view it on GitHub.

@nwhittaker
Copy link

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.

@jbates
Copy link

jbates commented May 28, 2014

+1
This got me, especially coupled with a Drupal base theme issue which made it really hard to get rid of old aggregated CSS that still had the debug blocks.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants