Fixes #11805 with docs mention of navbar

diff --git a/getting-started.html b/getting-started.html
index 5b88dfbe2947a6a144c413f90e76ea79df61dd22..be8bdb932961f1c239cd4b15eb027f3a68141e2b 100644 (file)
--- a/getting-started.html
+++ b/getting-started.html
@@ -868,11 +868,11 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
     </ul>
     <p>We'll keep an eye on this though and update our code if we have an easy solution.</p>
 
-    <h3 id="mobile-modals">Modals and mobile devices</h3>
+    <h3 id="mobile-modals">Modals, navbars, and mobile devices</h3>
     <h4>Overflow and scrolling</h4>
     <p>Support for <code>overflow: hidden</code> on the <code>&lt;body&gt;</code> element is quite limited in iOS and Android. To that end, when you scroll past the top or bottom of a modal in either of those devices' browsers, the <code>&lt;body&gt;</code> content will begin to scroll.</p>
     <h4>Virtual keyboards</h4>
-    <p>Also, note that if you're using inputs in your modal – iOS has a rendering bug that doesn't update the position of fixed elements when the virtual keyboard is triggered. A few workarounds for this include transforming your elements to <code>position: absolute</code> or invoking a timer on focus to try to correct the positioning manually. This is not handled by Bootstrap, so it is up to you to decide which solution is best for your application.</p>
+    <p>Also, note that if you're using inputs in your modal or navbar, iOS has a rendering bug that doesn't update the position of fixed elements when the virtual keyboard is triggered. A few workarounds for this include transforming your elements to <code>position: absolute</code> or invoking a timer on focus to try to correct the positioning manually. This is not handled by Bootstrap, so it is up to you to decide which solution is best for your application.</p>
 
     <h3 id="browser-zoom">Browser zooming</h3>
     <p>Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.</p>