From a925a0b985281ce34666c9a8a5630ba258904cb5 Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Sun, 15 Dec 2013 12:27:46 -0800 Subject: [PATCH] Browser/device support docs update * Fixes #11055: add mention of select menu styling on Android stock browsers with included optional fix * Update IDs and docs nav to include bookmark links to each section * Add callout to navbar docs about fixed position, inputs, and virtual keyboard --- _includes/nav-getting-started.html | 14 +++++++++++- components.html | 5 +++++ getting-started.html | 36 +++++++++++++++++++++--------- javascript.html | 4 ++-- 4 files changed, 46 insertions(+), 13 deletions(-) diff --git a/_includes/nav-getting-started.html b/_includes/nav-getting-started.html index ce7a718d66..6c041eef38 100644 --- a/_includes/nav-getting-started.html +++ b/_includes/nav-getting-started.html @@ -32,7 +32,19 @@
  • - Browser support + Browser and device support +
  • Third party support diff --git a/components.html b/components.html index 91495c38e9..5bbaf29112 100644 --- a/components.html +++ b/components.html @@ -2204,6 +2204,11 @@ base_url: "../" {% endhighlight %} +
    +

    Mobile device caveats

    +

    There are some caveats regarding using form controls within fixed elements on mobile devices. See our browser support docs for details.

    +
    +

    Always add labels

    Screen readers will have trouble with your forms if you don't include a label for every input. For these inline navbar forms, you can hide the labels using the .sr-only class.

    diff --git a/getting-started.html b/getting-started.html index be8bdb9329..d4b3c8cc1c 100644 --- a/getting-started.html +++ b/getting-started.html @@ -753,11 +753,11 @@ bootstrap/ ================================================== -->

    Bootstrap is built to work best in the latest desktop and mobile browsers, meaning older browsers might display differently styled, though fully functional, renderings of certain components.

    -

    Supported browsers

    +

    Supported browsers

    Specifically, we support the latest versions of the following:

    • Chrome (Mac, Windows, iOS, and Android)
    • @@ -768,7 +768,7 @@ bootstrap/

    Unofficially, Bootstrap should look and behave well enough in Chromium and Chrome for Linux, Firefox for Linux, and Internet Explorer 7, though they are not officially supported.

    -

    Internet Explorer 8 and 9

    +

    Internet Explorer 8 and 9

    Internet Explorer 8 and 9 are also supported, however, please be aware that some CSS3 properties and HTML5 elements are not fully supported by these browsers. In addition, Internet Explorer 8 requires the use of Respond.js to enable media query support.

    @@ -811,7 +811,7 @@ bootstrap/

    Visit Can I use... for details on browser support of CSS3 and HTML5 features.

    -

    Internet Explorer 8 and Respond.js

    +

    Internet Explorer 8 and Respond.js

    Beware of the following caveats when using Respond.js in your development and production environments for Internet Explorer 8.

    Respond.js and cross-domain CSS

    Using Respond.js with CSS hosted on a different (sub)domain (for example, on a CDN) requires some additional setup. See the Respond.js docs for details.

    @@ -820,10 +820,10 @@ bootstrap/

    Respond.js and @import

    Respond.js doesn't work with CSS that's referenced via @import. In particular, some Drupal configurations are known to use @import. See the Respond.js docs for details.

    -

    Internet Explorer 8 and box-sizing

    +

    Internet Explorer 8 and box-sizing

    IE8 does not fully support box-sizing: border-box; when combined with min-width, max-width, min-height, or max-height. For that reason, as of v3.0.1, we no longer use max-width on .containers.

    -

    IE Compatibility modes

    +

    IE Compatibility modes

    Bootstrap is not supported in the old Internet Explorer compatibility modes. To be sure you're using the latest rendering mode for IE, consider including the appropriate <meta> tag in your pages:

    {% highlight html %} @@ -832,7 +832,7 @@ bootstrap/

    This tag is included in all Bootstrap's documentation and examples to ensure the best rendering possible in each supported version of Internet Explorer.

    See this StackOverflow question for more information.

    -

    Internet Explorer 10 in Windows 8 and Windows Phone 8

    +

    Internet Explorer 10 in Windows 8 and Windows Phone 8

    Internet Explorer 10 doesn't differentiate device width from viewport width, and thus doesn't properly apply the media queries in Bootstrap's CSS. Normally you'd just add a quick snippet of CSS to fix this:

    {% highlight css %} @-ms-viewport { width: device-width; } @@ -860,7 +860,7 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {

    For more information and usage guidelines, read Windows Phone 8 and Device-Width.

    As a heads up, we include this in the Bootstrap docs as an example.

    -

    Safari percent rounding

    +

    Safari percent rounding

    As of Safari v6.1 for OS X and Safari for iOS v7.0.1, Safari's rendering engine has some trouble with the number of decimal places used in our .col-*-1 grid classes. So if you have 12 individual grid columns, you'll notice that they come up short compared to other rows of columns. We can't do much here (see #9282) but you do have some options:

    • Add .pull-right to your last grid column to get the hard-right alignment
    • @@ -868,14 +868,30 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {

    We'll keep an eye on this though and update our code if we have an easy solution.

    -

    Modals, navbars, and mobile devices

    +

    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.

    Virtual keyboards

    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 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.

    -

    Browser zooming

    +

    Browser zooming

    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.

    + +

    Android stock browser

    +

    Out of the box, Android 4.1 (and even some newer releases apparently) ship with the Browser app as the default web browser of choice (as opposed to Chrome). Unfortunately, the Browser app has lots of bugs and inconsistencies with CSS in general.

    +

    Select menus

    +

    On <select> elements, the Android stock browser will not display the side controls if there is a border-radius and/or border applied. Use the snippet of code below to remove the offending CSS and render the <select> as an unstyled element on the Android stock broswer. The useragent sniffing avoids interfernece with Chrome, Safari, and Mozilla browsers.

    +{% highlight html %} + +{% endhighlight %} +

    Want to see an example? Check out this JS Bin demo.

    + diff --git a/javascript.html b/javascript.html index 76c9807ebf..d83358a397 100644 --- a/javascript.html +++ b/javascript.html @@ -74,7 +74,7 @@ $('#myModal').on('show.bs.modal', function (e) {

    Third-party libraries

    -

    Bootstrap does not officially support third-party JavaScript libraries like Prototype or jQuery UI. Despite .noConflict and namespaced events, there may be compatibility problems that you need to fix on your own. Ask on the mailing list if you need help.

    +

    Bootstrap does not officially support third-party JavaScript libraries like Prototype or jQuery UI. Despite .noConflict and namespaced events, there may be compatibility problems that you need to fix on your own.

    @@ -110,7 +110,7 @@ $('#myModal').on('show.bs.modal', function (e) {

    Mobile device caveats

    -

    There are some caveats regarding using modals on mobile devices. See our browser support docs for details.

    +

    There are some caveats regarding using modals on mobile devices. See our browser support docs for details.

    Static example