From: Chris Rebert Date: Mon, 7 Mar 2016 05:03:46 +0000 (-0800) Subject: Port #19423 to v3 X-Git-Tag: v3.3.7~104 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=164b89f7af4221ae3cb078ada467230780e7f5aa;p=thirdparty%2Fbootstrap.git Port #19423 to v3 Docs: Add link to Chrome bug regarding `body { overflow: hidden; }` https://bugs.chromium.org/p/chromium/issues/detail?id=175502 [skip sauce] --- diff --git a/docs/_includes/getting-started/browser-device-support.html b/docs/_includes/getting-started/browser-device-support.html index e98998ce19..4b47a11cb9 100644 --- a/docs/_includes/getting-started/browser-device-support.html +++ b/docs/_includes/getting-started/browser-device-support.html @@ -184,7 +184,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. See WebKit bug #153852.

+

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 Chrome bug #175502 (fixed in Chrome v40) and 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