Browsers and devices
Learn about the browsers and devices, from modern to old, that are supported by Bootstrap, including known quirks and bugs for each.
已支持的浏览器
Bootstrap 支持所有 最新、稳定版本的 主流浏览器和平台。在 Windows 上，我们支持 Internet Explorer 10-11 / Microsoft Edge 浏览器。
使用最新版本 WebKit、Blink 或 Gecko 的第三方浏览器，无论是直接还是通过平台上的 web view API 实现的，Bootstrap 官方虽未明确支持。但是，Bootstrap 在这些浏览器上应当（大部分情况下）是能够正常显示或运行的。
移动设备
Generally speaking, Bootstrap supports the latest versions of each major platform’s default browsers. Note that proxy browsers (such as Opera Mini, Opera Mobile’s Turbo mode, UC Browser Mini, Amazon Silk) are not supported. 一般而言，Bootstrap 支持主流平台上的最新版本的默认浏览器。注意，代理模式的浏览器（例如 Opera Mini、Opera Mobile’s Turbo mode、UC Browser Mini、Amazon Silk）是不被支持的。
| Chrome | Firefox | Safari | Android Browser & WebView | Microsoft Edge | |
|---|---|---|---|---|---|
| Android | 支持 | 支持 | N/A | Android v5.0+ 版本支持 | 支持 |
| iOS | 支持 | 支持 | 支持 | N/A | 支持 |
| Windows 10 Mobile | N/A | N/A | N/A | N/A | 支持 |
桌面浏览器
同样的，大部分最新版本的桌面浏览器是被支持的。
| Chrome | Firefox | Internet Explorer | Microsoft Edge | Opera | Safari | |
|---|---|---|---|---|---|---|
| Mac | 支持 | 支持 | N/A | N/A | 支持 | 支持 |
| Windows | 支持 | 支持 | 支持, IE10+ | 支持 | 支持 | 不支持 |
对于 Firefox，除了最新版的通用稳定版本外，我们还支持最新的 扩充支持发布 (ESR) 版本的 Firefox。
一般情况下，Bootstrap 在 Chromium 和 Chrome for Linux、Firefox for Linux 以及 Internet Explorer 9 浏览器上能够很好的运行，不过这些浏览器并没有在官方支持之列。
Bootstrap 对某些浏览器的 bug 也无可奈何，先在 浏览器 bug 列表 上记下这笔账。
Internet Explorer 浏览器
Internet Explorer 10+ 是被支持的；IE9 及更低版本不被支持。请注意，某些 CSS3 属性和 HTML5 元素并不完全被 IE10 支持，或者需要添加特定前缀才能够正常工作。请参考 Can I use… 网站以了解各浏览器对 CSS3 和 HTML5 特性的支持情况。
如果你的确需要支持 IE8-9 ，请继续使用 Bootstrap 3 吧。 这是我们最稳定的版本，并且仍然被我们的团队所支持，虽然不再为其增加新特性了，但是仍然提供对严重 bug 的修复和文档更新。
移动设备上的模态框和下拉菜单
溢出（Overflow） 和 滚动
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.
iOS text fields and scrolling
As of iOS 9.2, while a modal is open, if the initial touch of a scroll gesture is within the boundary of a textual <input> or a <textarea>, the <body> content underneath the modal will be scrolled instead of the modal itself. See WebKit bug #153856.
Navbar Dropdowns
The .dropdown-backdrop 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).
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.
Sticky :hover/:focus on iOS
While :hover isn’t possible on most touch devices, iOS emulates this behavior, resulting in “sticky” hover styles that persist after tapping one element. These hover styles are only removed when users tap another element. This behavior is considered largely undesirable and appears to not be an issue on Android or Windows devices.
Throughout our v4 alpha and beta releases, we included incomplete and commented out code for opting into a media query shim that would disable hover styles in touch device browsers that emulate hovering. This work was never fully completed or enabled, but to avoid complete breakage, we’ve opted to deprecate this shim and keep the mixins as shortcuts for the pseudo-classes.
Printing
Even in some modern browsers, printing can be quirky.
As of Safari v8.0, use of the fixed-width .container class can cause Safari to use an unusually small font size when printing. See issue #14868 and WebKit bug #138192 for more details. One potential workaround is the following CSS:
@media print {
.container {
width: auto;
}
}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 menu
On <select> elements, the Android stock browser will not display the side controls if there is a border-radius and/or border applied. (See this StackOverflow question for details.) Use the snippet of code below to remove the offending CSS and render the <select> as an unstyled element on the Android stock browser. The user agent sniffing avoids interference with Chrome, Safari, and Mozilla browsers.
<script>
$(function () {
var nua = navigator.userAgent
var isAndroid = (nua.indexOf('Mozilla/5.0') > -1 && nua.indexOf('Android ') > -1 && nua.indexOf('AppleWebKit') > -1 && nua.indexOf('Chrome') === -1)
if (isAndroid) {
$('select.form-control').removeClass('form-control').css('width', '100%')
}
})
</script>Want to see an example? Check out this JS Bin demo.
Validators
In order to provide the best possible experience to old and buggy browsers, Bootstrap uses CSS browser hacks in several places to target special CSS to certain browser versions in order to work around bugs in the browsers themselves. These hacks understandably cause CSS validators to complain that they are invalid. In a couple places, we also use bleeding-edge CSS features that aren’t yet fully standardized, but these are used purely for progressive enhancement.
These validation warnings don’t matter in practice since the non-hacky portion of our CSS does fully validate and the hacky portions don’t interfere with the proper functioning of the non-hacky portion, hence why we deliberately ignore these particular warnings.
Our HTML docs likewise have some trivial and inconsequential HTML validation warnings due to our inclusion of a workaround for a certain Firefox bug.