Document shitty situation of multiple .navbar-right classes in #12951

diff --git a/docs/components.html b/docs/components.html
index f70ceedc3f00cdf05a0ca018ec3fbbb7c0c341ed..ad145604faa4753d63a2e4bbca4b1bab3fc11c11 100644 (file)
--- a/docs/components.html
+++ b/docs/components.html
@@ -1535,6 +1535,11 @@ lead: "Over a dozen reusable components built to provide iconography, dropdowns,
   <h2 id="navbar-component-alignment">Component alignment</h2>
   <p>Align nav links, forms, buttons, or text, using the <code>.navbar-left</code> or <code>.navbar-right</code> utility classes. Both classes will add a CSS float in the specified direction. For example, to align nav links, put them in a separate <code>&lt;ul&gt;</code> with the respective utility class applied.</p>
   <p>These classes are mixin-ed versions of <code>.pull-left</code> and <code>.pull-right</code>, but they're scoped to media queries for easier handling of navbar components across device sizes.</p>
+  <div class="bs-callout bs-callout-warning">
+    <h4>Right aligning multiple components</h4>
+    <p>Navbars currently have a limitation with multiple <code>.navbar-right</code> classes. To properly space content, we use negative margin on the last <code>.navbar-right</code> element. When there are multiple elements using that class, these margins don't work as intended.</p>
+    <p>We'll revisit this when we can rewrite that component in v4.</p>
+  </div>
 
 
   <h2 id="navbar-fixed-top">Fixed to top</h2>