aboutsummaryrefslogtreecommitdiff
path: root/getting-started.html
diff options
context:
space:
mode:
authorfat <[email protected]>2013-12-29 19:40:31 -0800
committerfat <[email protected]>2013-12-29 19:40:31 -0800
commitd18ba5083785052f37bc9e929fb315b144e88987 (patch)
tree8e86071bde988d4c8d86cf3846092b268ff122e2 /getting-started.html
parent1fea9656b604cd23e42be928e398969320b3b5ff (diff)
downloadbootstrap-d18ba5083785052f37bc9e929fb315b144e88987.tar.xz
bootstrap-d18ba5083785052f37bc9e929fb315b144e88987.zip
add note about ios dropdown compat
Diffstat (limited to 'getting-started.html')
-rw-r--r--getting-started.html2
1 files changed, 2 insertions, 0 deletions
diff --git a/getting-started.html b/getting-started.html
index 73a2159f2..b15b120d9 100644
--- a/getting-started.html
+++ b/getting-started.html
@@ -873,6 +873,8 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
<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 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>
+ <h4>Navbar Dropdowns</h4>
+ <p>The <code>.dropdown-backdrop</code> element isn't used on ios in the nav because of the complexity of z-indexing. Thus, to close dropdowns in navbars you must directly click the dropdown element (or any other element which will fire a click event in ios).</p>
<h3 id="support-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>