From: Mark Otto
Date: Sun, 29 Mar 2015 07:08:54 +0000 (-0700)
Subject: Merge branch 'master' into v4
X-Git-Tag: v4.0.0-alpha~332
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=58082cd83e9244fa05f316b4ba4102891ff5b0aa;p=thirdparty%2Fbootstrap.git
Merge branch 'master' into v4
Conflicts:
.gitignore
Gruntfile.js
_config.yml
dist/css/bootstrap-theme.css
dist/css/bootstrap-theme.min.css
dist/css/bootstrap.css
dist/css/bootstrap.css.map
dist/css/bootstrap.min.css
dist/js/bootstrap.js
dist/js/bootstrap.min.js
docs/_includes/components/navbar.html
docs/_includes/components/progress-bars.html
docs/_includes/css/grid.html
docs/_includes/css/overview.html
docs/_includes/customizer-variables.html
docs/_includes/getting-started/accessibility.html
docs/_includes/getting-started/browser-device-support.html
docs/_includes/getting-started/community.html
docs/_includes/getting-started/disabling-responsiveness.html
docs/_includes/getting-started/download.html
docs/_includes/getting-started/examples.html
docs/_includes/getting-started/license.html
docs/_includes/getting-started/third-party-support.html
docs/_includes/js/alerts.html
docs/_includes/js/buttons.html
docs/_includes/js/carousel.html
docs/_includes/js/collapse.html
docs/_includes/js/dropdowns.html
docs/_includes/js/modal.html
docs/_includes/js/popovers.html
docs/_includes/js/scrollspy.html
docs/_includes/js/tabs.html
docs/_includes/js/tooltips.html
docs/_includes/js/transitions.html
docs/_includes/nav/javascript.html
docs/_includes/nav/main.html
docs/about.html
docs/assets/css/docs.min.css
docs/assets/css/src/docs.css
docs/assets/js/customize.min.js
docs/assets/js/raw-files.min.js
docs/assets/js/src/customizer.js
docs/dist/css/bootstrap-theme.css
docs/dist/css/bootstrap-theme.min.css
docs/dist/css/bootstrap.css
docs/dist/css/bootstrap.css.map
docs/dist/css/bootstrap.min.css
docs/dist/js/bootstrap.js
docs/dist/js/bootstrap.min.js
docs/migration.html
js/affix.js
js/alert.js
js/button.js
js/carousel.js
js/collapse.js
js/dropdown.js
js/modal.js
js/popover.js
js/scrollspy.js
js/tab.js
js/tests/unit/affix.js
js/tests/unit/button.js
js/tests/unit/carousel.js
js/tests/unit/modal.js
js/tests/unit/tooltip.js
js/tests/visual/modal.html
js/tooltip.js
less/component-animations.less
less/jumbotron.less
less/mixins/background-variant.less
less/mixins/buttons.less
less/mixins/responsive-visibility.less
less/mixins/text-emphasis.less
less/navbar.less
less/navs.less
less/scaffolding.less
less/tooltip.less
less/utilities.less
less/variables.less
package.json
scss/_buttons.scss
scss/_forms.scss
scss/_modal.scss
---
58082cd83e9244fa05f316b4ba4102891ff5b0aa
diff --cc Gruntfile.js
index a934eec88c,b715189a94..a54d4781b2
--- a/Gruntfile.js
+++ b/Gruntfile.js
@@@ -244,18 -201,49 +244,21 @@@ module.exports = function (grunt)
}
},
- csslint: {
- options: {
- csslintrc: 'less/.csslintrc'
- },
- dist: [
- 'dist/css/bootstrap.css',
- 'dist/css/bootstrap-theme.css'
- ],
- examples: [
- 'docs/examples/**/*.css'
- ],
- docs: {
- options: {
- ids: false,
- 'overqualified-elements': false
- },
- src: 'docs/assets/css/src/docs.css'
- }
- },
-
cssmin: {
options: {
+ // TODO: disable `zeroUnits` optimization once clean-css 3.2 is released
+ // and then simplify the fix for https://github.com/twbs/bootstrap/issues/14837 accordingly
+ compatibility: 'ie8',
keepSpecialComments: '*',
- advanced: false
- },
- minifyCore: {
- src: 'dist/css/<%= pkg.name %>.css',
- dest: 'dist/css/<%= pkg.name %>.min.css'
+ noAdvanced: true
},
- minifyTheme: {
- src: 'dist/css/<%= pkg.name %>-theme.css',
- dest: 'dist/css/<%= pkg.name %>-theme.min.css'
+ core: {
+ files: {
+ 'dist/css/<%= pkg.name %>.min.css': 'dist/css/<%= pkg.name %>.css'
+ }
},
docs: {
- src: [
- 'docs/assets/css/src/pygments-manni.css',
- 'docs/assets/css/src/anchor.css',
- 'docs/assets/css/src/docs.css'
-
- ],
+ src: 'docs/assets/css/docs.min.css',
dest: 'docs/assets/css/docs.min.css'
}
},
diff --cc _config.yml
index 1f63b36f9d,839bc7593f..6dd22ada88
--- a/_config.yml
+++ b/_config.yml
@@@ -32,12 -27,6 +32,12 @@@ blog: http://blog.getbootst
expo: http://expo.getbootstrap.com
cdn:
- css: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.2/css/bootstrap.min.css
- js: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.2/js/bootstrap.min.js
+ css: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css
- css_theme: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap-theme.min.css
+ js: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js
+ jquery: //code.jquery.com/jquery-2.1.1.min.js
+
+bug:
+ firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=
+ webkit: https://bugs.webkit.org/show_bug.cgi?id=
+ chrome: https://code.google.com/p/chromium/issues/detail?id=
+ github: https://github.com/twbs/bootstrap/issues/
diff --cc docs/about/history.md
index a2c9db14be,0000000000..7d881fe07c
mode 100644,000000..100644
--- a/docs/about/history.md
+++ b/docs/about/history.md
@@@ -1,10 -1,0 +1,10 @@@
+---
+layout: page
+title: History
+---
+
+Originally created by a designer and a developer at Twitter, Bootstrap has become one of the most popular front-end frameworks and open source projects in the world.
+
+Bootstrap was created at Twitter in mid-2010 by [@mdo](https://twitter.com/mdo) and [@fat](https://twitter.com/fat). Prior to being an open-sourced framework, Bootstrap was known as _Twitter Blueprint_. A few months into development, Twitter held its [first Hack Week](https://blog.twitter.com/2010/hack-week) and the project exploded as developers of all skill levels jumped in without any external guidance. It served as the style guide for internal tools development at the company for over a year before its public release, and continues to do so today.
+
- Originally [released](https://dev.twitter.com/blog/bootstrap-twitter) on [](https://twitter.com/mdo/statuses/104620039650557952), we've since had over [twenty releases](https://github.com/twbs/bootstrap/releases), including two major rewrites with v2 and v3. With Bootstrap 2, we added responsive functionality to the entire framework as an optional stylesheet. Building on that with Bootstrap 3, we rewrote the library once more to make it responsive by default with a mobile first approach.
++Originally [released](https://blog.twitter.com/2011/bootstrap-twitter) on [](https://twitter.com/mdo/statuses/104620039650557952), we've since had over [twenty releases](https://github.com/twbs/bootstrap/releases), including two major rewrites with v2 and v3. With Bootstrap 2, we added responsive functionality to the entire framework as an optional stylesheet. Building on that with Bootstrap 3, we rewrote the library once more to make it responsive by default with a mobile first approach.
diff --cc docs/getting-started/accessibility.md
index c1a23da350,0000000000..c20085ff85
mode 100644,000000..100644
--- a/docs/getting-started/accessibility.md
+++ b/docs/getting-started/accessibility.md
@@@ -1,38 -1,0 +1,38 @@@
+---
+layout: page
+title: Accessibility
+---
+
+Bootstrap follows common web standards andâwith minimal extra effortâcan be used to create sites that are accessible to those using AT.
+
- ### Skip navigation
++## Skip navigation
+
+If your navigation contains many links and comes before the main content in the DOM, add a `Skip to main content` link before the navigation (for a simple explanation, see this [A11Y Project article on skip navigation links](http://a11yproject.com/posts/skip-nav-links/)). Using the `.sr-only` class will visually hide the skip link, and the .sr-only-focusable class will ensure that the link becomes visible once focused (for sighted keyboard users).
+
+
+
Due to long-standing shortcomings/bugs in Chrome (see issue 262171 in the Chromium bug tracker) and Internet Explorer (see this article on in-page links and focus order), you will need to make sure that the target of your skip link is at least programmatically focusable by adding tabindex="-1".
+
In addition, you may want to explicitly suppress a visible focus indication on the target (particularly as Chrome currently also sets focus on elements with tabindex="-1" when they are clicked with the mouse) with #content:focus { outline: none; }.
+
Note that this bug will also affect any other in-page links your site may be using, rendering them useless for keyboard users. You may consider adding a similar stop-gap fix to all other named anchors / fragment identifiers that act as link targets.
`. Subsequent headings should make logical use of `
` - `
` such that screen readers can construct a table of contents for your pages.
+
+Learn more at [HTML CodeSniffer](http://squizlabs.github.io/HTML_CodeSniffer/Standards/Section508/) and [Penn State's Accessability](http://accessibility.psu.edu/headings).
+
- ### Additional resources
++## Additional resources
+
+- ["HTML Codesniffer" bookmarklet for identifying accessibility issues](https://github.com/squizlabs/HTML_CodeSniffer)
+- [The A11Y Project](http://a11yproject.com/)
+- [MDN accessibility documentation](https://developer.mozilla.org/en-US/docs/Accessibility)
diff --cc docs/getting-started/download.md
index 6bcf8dd009,0000000000..8bebeea4cc
mode 100644,000000..100644
--- a/docs/getting-started/download.md
+++ b/docs/getting-started/download.md
@@@ -1,59 -1,0 +1,72 @@@
+---
+layout: page
+title: Download
+---
+
+Bootstrap is available for download via ZIP file in two flavors: precompiled CSS and Javascript, and the complete source code with documentation.
+
+{% comment %}
+## Optional builds
+
+### Scaffolding only
+Just our global CSS resets, including Normalize and more. No custom CSS components or JavaScript.
+
+### Grid only
+Literally just our grid container and columns. No global CSS resets, custom CSS components, or JavaScript.
+
+### Individual components
+Choose what CSS and JS components to download and customize further for your own use. Include the global CSS resets.
+
+### Kitchen sink
+Download the entire project and quickly get developing. Includes all CSS and JavaScript, including the source files and basic build tools.
+
+---
+{% endcomment %}
+
+### Precompiled
+
+Compiled and minified CSS and JavaScript. No docs or original source files are included.
+
+Download Bootstrap
+
+### Download source and docs
+
+Source Sass, JavaScript, and documentation. **Requires a Sass compiler and [some setup](../compiling).**
+
+Download source
+
+### Bower
+
+You can also install and manage Bootstrap's Sass, CSS, and JavaScript using [Bower](http://bower.io).
+
+{% highlight bash %}$ bower install bootstrap{% endhighlight %}
+
+### npm
+
+Bootstrap is available as [an npm package](https://www.npmjs.org/package/bootstrap). Install it into your Node powered apps with:
+
+{% highlight bash %}$ npm install bootstrap{% endhighlight %}
+
+`require('bootstrap')` will load all of Bootstrap's jQuery plugins onto the jQuery object. The `bootstrap` module itself does not export anything. You can manually load Bootstrap's jQuery plugins individually by loading the `/js/*.js` files under the package's top-level directory.
+
+Bootstrap's `package.json` contains some additional metadata under the following keys:
+
+- `less` - path to Bootstrap's main [Less](http://lesscss.org) source file
+- `style` - path to Bootstrap's non-minified CSS that's been precompiled using the default settings (no customization)
+
++### Meteor
++
++{% highlight bash %}
++$ meteor add twbs:bootstrap
++{% endhighlight %}
++
++### Composer
++
++{% highlight bash %}
++$ composer require twbs/bootstrap
++{% endhighlight %}
++
++
+### Autoprefixer required
+
+Bootstrap uses [Autoprefixer](https://github.com/postcss/autoprefixer) to deal with [CSS vendor prefixes](http://webdesign.about.com/od/css/a/css-vendor-prefixes.htm). If you're compiling Bootstrap from its source Sass and not using our Gruntfile, you'll need to integrate Autoprefixer into your build process yourself. If you're using precompiled Bootstrap or using our Gruntfile, you don't need to worry about this as Autoprefixer is already integrated into our Gruntfile.
diff --cc docs/getting-started/support.md
index 2a96dbef70,0000000000..cf87535baf
mode 100644,000000..100644
--- a/docs/getting-started/support.md
+++ b/docs/getting-started/support.md
@@@ -1,218 -1,0 +1,218 @@@
+---
+layout: page
+title: Supported platforms
+---
+
+Bootstrap is built to work best with the latest techniques. As such, older desktop and mobile browsers may display differently, but should remain fully functional.
+
- ### Supported browsers
++## Supported browsers
+
+Bootstrap supports the **latest, stable releases** of all major browsers and platforms. On Windows, **we support Internet Explorer 9-11**. More specific support information is provided below.
+
+
+
+
+
+
+
Chrome
+
Firefox
+
Internet Explorer
+
Opera
+
Safari
+
Android Browser & WebView
+
+
+
+
+
Android
+
Supported
+
Supported
+
N/A
+
Not supported
+
N/A
+
Android v5.0+ supported
+
+
+
iOS
+
Supported
+
N/A
+
Not supported
+
Supported
+
N/A
+
+
+
Mac OS X
+
Supported
+
Supported
+
Supported
+
Supported
+
N/A
+
+
+
Windows
+
Supported
+
Supported
+
Supported
+
Supported
+
Not supported
+
N/A
+
+
+
+
+
+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.
+
+For a list of some of the browser bugs that Bootstrap has to grapple with, see our [Wall of browser bugs](../browser-bugs/).
+
- ### Internet Explorer 9
++## Internet Explorer 9
+
+Internet Explorer 9 is also supported, however, please be aware that some CSS3 properties and HTML5 elements are not fully supported.
+
+
+
+
+
+
Feature
+
Status
+
+
+
+
+
border-radius
+
Supported
+
+
+
box-shadow
+
Supported
+
+
+
transform
+
Supported, with -ms prefix
+
+
+
transition
+
Not supported
+
+
+
placeholder
+
Not supported
+
+
+
+
+
+Visit [Can I use...](http://caniuse.com/) for details on browser support of CSS3 and HTML5 features.
+
- ### Supporting Internet Explorer 8
++## Supporting Internet Explorer 8
+
+As of v4, Bootstrap no longer supports IE8. **If you require IE8 support, we recommend you use Bootstrap 3.** It's still supported by our team for bugfixes and documentation changes, but no new features will be added to it.
+
+Alternatively, you can add the some third party JavaScript to backfill support for the browser. You'll need the following:
+
+* [The HTML5 shiv](http://en.wikipedia.org/wiki/HTML5_Shiv)
+* [Respond.js](https://github.com/scottjehl/Respond)
+* [Rem unit polyfill](https://github.com/chuckcarpenter/REM-unit-polyfill)
+
- ### 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 `` tag in your pages:
+
+{% highlight html %}
+
+{% endhighlight %}
+
+Confirm the document mode by opening the debugging tools: press F12 and check the "Document Mode".
+
+This tag is included in all of Bootstrap's documentation and examples to ensure the best rendering possible in each supported version of Internet Explorer.
+
+See [this StackOverflow question](http://stackoverflow.com/questions/6771258/whats-the-difference-if-meta-http-equiv-x-ua-compatible-content-ie-edge) for more information.
+
- ### Internet Explorer 10 in Windows Phone 8
++## Internet Explorer 10 in Windows Phone 8
+
+Internet Explorer 10 in Windows Phone 8 versions older than [Update 3 (a.k.a. GDR3)](http://blogs.windows.com/windows_phone/b/wpdev/archive/2013/10/14/introducing-windows-phone-preview-for-developers.aspx) doesn't differentiate **device width** from **viewport width** in `@-ms-viewport` at-rules, and thus doesn't properly apply the media queries in Bootstrap's CSS. To address this, you'll need to **include the following JavaScript to work around the bug**.
+
+{% highlight js %}
+if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
+ var msViewportStyle = document.createElement('style')
+ msViewportStyle.appendChild(
+ document.createTextNode(
+ '@-ms-viewport{width:auto!important}'
+ )
+ )
+ document.querySelector('head').appendChild(msViewportStyle)
+}
+{% endhighlight %}
+
+For more information and usage guidelines, read [Windows Phone 8 and Device-Width](http://timkadlec.com/2013/01/windows-phone-8-and-device-width/).
+
+As a heads up, we include this in all of Bootstrap's documentation and examples as a demonstration.
+
- ### Modals, navbars, and virtual keyboards
++## Modals, navbars, and virtual keyboards
+
- #### Overflow and scrolling
++### Overflow and scrolling
+
+Support for `overflow: hidden;` on the `` 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 `` content will begin to scroll.
+
- #### Virtual keyboards
++### 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
++### 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](https://developer.mozilla.org/en-US/docs/Web/Events/click#Safari_Mobile)).
+
- ### 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.
+
- ### Sticky `:hover`/`:focus` on mobile
++## Sticky `:hover`/`:focus` on mobile
+Even though real hovering isn't possible on most touchscreens, most mobile browsers emulate hovering support and make `:hover` "sticky". In other words, `:hover` styles start applying after tapping an element and only stop applying after the user taps some other element. On mobile-first sites, this behavior is normally undesirable.
+
+Bootstrap includes a workaround for this, although it is disabled by default. By setting `$use-hover-media-query` to `true` when compiling from Sass, Bootstrap will use [mq4-hover-shim](https://github.com/twbs/mq4-hover-shim) to disable `:hover` styles in browsers that emulate hovering, thus preventing sticky `:hover` styles. There are some caveats to this workaround; see the shim's documentation for details.
+
- ### Printing
++## Printing
+
+Even in some modern browsers, printing can be quirky.
+
+In particular, as of Chrome v32 and regardless of margin settings, Chrome uses a viewport width significantly narrower than the physical paper size when resolving media queries while printing a webpage. This can result in Bootstrap's extra-small grid being unexpectedly activated when printing. [See #12078 for some details.](https://github.com/twbs/bootstrap/issues/12078) Suggested workarounds:
+
+Also, as of Safari v8.0, fixed-width .containers can cause Safari to use an unusually small font size when printing. See #14868 for more details. One potential workaround for this is adding the following CSS:
+
+{% highlight css %}
+@media print {
+ .container {
+ width: auto;
+ }
+}
+{% endhighlight %}
+
- ### Android stock browser
++## 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 `