From 0f5170e08d2acf1f88df25b46559421e0fd467b5 Mon Sep 17 00:00:00 2001 From: Steven Xu Date: Fri, 21 Feb 2014 15:33:10 -0800 Subject: [PATCH] Added gotcha remarks on default yeoman webapp generator producing sass debug blocks breaking respond.js. This hopefully helps out developers who have sass debug blocks enabled out of the box without explicitly enabling them (so that they might not recognize this caveat line when they first see it). The related discussion was in #148. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2cdc7c29..dfdfd245 100644 --- a/README.md +++ b/README.md @@ -85,7 +85,7 @@ respond with a 200 status. - If you have more than 32 stylesheets referenced, IE will throw an error, `Invalid procedure call or argument`. Concatenate your CSS and the issue should go away. -- Sass/SCSS source maps are not supported; `@media -sass-debug-info` will break respond.js. Noted in issue [#148](https://github.com/scottjehl/Respond/issues/148) +- Sass/SCSS source maps are not supported; `@media -sass-debug-info` will break respond.js. Noted in issue [#148](https://github.com/scottjehl/Respond/issues/148). Source maps may be enabled by default in apps produced by the [Yeoman webapp generator](https://github.com/yeoman/generator-webapp) but can be disabled by removing the `debugInfo` override in the Gruntfile. - Internet Explorer 9 supports css3 media queries, but not within frames when the CSS containing the media query is in an external file (this appears to be a bug in IE9 — see http://stackoverflow.com/questions/10316247/media-queries-fail-inside-ie9-iframe). See this commit for a fix if you're having this problem. https://github.com/NewSignature/Respond/commit/1c86c66075f0a2099451eb426702fc3540d2e603