From b52ef829c188b946bff1c643cea70ce0c8a9439e Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Wed, 3 Feb 2016 22:58:46 -0800 Subject: [PATCH] Port #19078 to v3 [skip sauce] --- docs/_includes/getting-started/browser-device-support.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_includes/getting-started/browser-device-support.html b/docs/_includes/getting-started/browser-device-support.html index 43c2e5349e..e4fdef870d 100644 --- a/docs/_includes/getting-started/browser-device-support.html +++ b/docs/_includes/getting-started/browser-device-support.html @@ -157,7 +157,7 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {

Modals, navbars, and virtual keyboards

Overflow and scrolling

-

Support for overflow: hidden on the <body> 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 <body> content will begin to scroll.

+

Support for overflow: hidden on the <body> 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 <body> content will begin to scroll. See WebKit bug #153852.

Virtual keyboards

Also, note that if you're using a fixed navbar or using inputs within a 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 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.

Navbar Dropdowns