From 53c80ed9cbeff8a3c58abe0f824ff68ef56d617a Mon Sep 17 00:00:00 2001
From: fat <jacobthornton@gmail.com>
Date: Sat, 17 Aug 2013 13:40:28 -0700
Subject: add comment addressing #9023

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

(limited to 'getting-started.html')

diff --git a/getting-started.html b/getting-started.html
index d19055052..ea5f96e61 100644
--- a/getting-started.html
+++ b/getting-started.html
@@ -365,6 +365,7 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
 
     <h3>Modals and mobile devices</h3>
     <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>
+    <p>Also, note that if you're using inputs in your modal – iOS has a rendering bug which doesn't update the position of fixed elements when the virtual keyboard is triggered. There are a few work arounds for this including transforming your elements to position absolute 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>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>
-- 
cgit v1.2.3