From d1dd1fcdee3a081dc2aa9874ba20ae5584652a01 Mon Sep 17 00:00:00 2001
From: Chris Rebert <code@rebertia.com>
Date: Mon, 28 Oct 2013 11:07:56 -0700
Subject: [PATCH] add warning about Respond.js not supporting @import; fixes
 #11143

---
 getting-started.html | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/getting-started.html b/getting-started.html
index ec3462f0e2..9eb820dffb 100644
--- a/getting-started.html
+++ b/getting-started.html
@@ -713,6 +713,10 @@ bootstrap/
       <h4>Respond.js and <code>file://</code></h4>
       <p>Due to browser security rules, Respond.js doesn't work with pages viewed via the <code>file://</code> protocol (like when opening a local HTML file). To test responsive features in IE8, view your pages over HTTP(S). <a href="https://github.com/scottjehl/Respond/blob/master/README.md#support--caveats">See the Respond.js docs</a> for details.</p>
     </div>
+    <div class="bs-callout bs-callout-warning" id="respond-import">
+      <h4>Respond.js and <code>@import</code></h4>
+      <p>Respond.js doesn't work with CSS that's referenced via <code>@import</code>. In particular, some Drupal configurations are known to use <code>@import</code>. <a href="https://github.com/scottjehl/Respond/blob/master/README.md#support--caveats">See the Respond.js docs</a> for details.</p>
+    </div>
     <div class="table-responsive">
       <table class="table table-bordered table-striped">
         <thead>
-- 
2.47.2