diff --git a/README.md b/README.md
index 717e3b9c15..1086a38e41 100644
--- a/README.md
+++ b/README.md
@@ -24,4 +24,4 @@
**[Head to the default branch for guidance on local development, contributing, support, and more.](https://github.com/twbs/bootstrap/)**
-Code and documentation copyright 2011-2019 the [Bootstrap Authors](https://github.com/twbs/bootstrap/graphs/contributors) and [Twitter, Inc.](https://twitter.com) Code released under the [MIT License](https://github.com/twbs/bootstrap/blob/master/LICENSE). Docs released under [Creative Commons](https://github.com/twbs/bootstrap/blob/master/docs/LICENSE).
+Code and documentation copyright 2011-2019 the [Bootstrap Authors](https://github.com/twbs/bootstrap/graphs/contributors) and [Twitter, Inc.](https://twitter.com) Code released under the [MIT License](https://github.com/twbs/bootstrap/blob/main/LICENSE). Docs released under [Creative Commons](https://github.com/twbs/bootstrap/blob/main/docs/LICENSE).
diff --git a/docs/3.3/about/index.html b/docs/3.3/about/index.html
index d9e061c54e..9b92e9e577 100644
--- a/docs/3.3/about/index.html
+++ b/docs/3.3/about/index.html
@@ -1 +1 @@
- About · Bootstrap
Learn about the project's history, meet the maintaining teams, and find out how to use the Bootstrap brand.
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 and @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 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 on Friday, August 19, 2011, we've since had over twenty 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.
Team
Bootstrap is maintained by the founding team and a small group of invaluable core contributors, with the massive support and involvement of our community.
Get involved with Bootstrap development by opening an issue or submitting a pull request. Read our contributing guidelines for information on how we develop.
The official Sass port of Bootstrap was created and is maintained by this team. It became part of Bootstrap's organization with v3.1.0. Read the Sass contributing guidelines for information on how the Sass port is developed.
Brand guidelines
Have a need for Bootstrap's brand resources? Great! We have only a few guidelines we follow, and in turn ask you to follow as well. These guidelines were inspired by MailChimp's Brand Assets.
Mark and logo
Use either the Bootstrap mark (a capital B) or the standard logo (just Bootstrap). It should always appear in Helvetica Neue Bold. Do not use the Twitter bird in association with Bootstrap.
B
B
Bootstrap
Bootstrap
Download mark
Download the Bootstrap mark in one of three styles, each available as an SVG file. Right click, Save as.
Name
The project and framework should always be referred to as Bootstrap. No Twitter before it, no capital s, and no abbreviations except for one, a capital B.
Bootstrap
(correct)
BootStrap
(incorrect)
Twitter Bootstrap
(incorrect)
Colors
Our docs and branding use a handful of primary colors to differentiate what is Bootstrap from what is in Bootstrap. In other words, if it's purple, it's representative of Bootstrap.
Learn about the project's history, meet the maintaining teams, and find out how to use the Bootstrap brand.
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 and @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 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 on Friday, August 19, 2011, we've since had over twenty 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.
Team
Bootstrap is maintained by the founding team and a small group of invaluable core contributors, with the massive support and involvement of our community.
Get involved with Bootstrap development by opening an issue or submitting a pull request. Read our contributing guidelines for information on how we develop.
The official Sass port of Bootstrap was created and is maintained by this team. It became part of Bootstrap's organization with v3.1.0. Read the Sass contributing guidelines for information on how the Sass port is developed.
Brand guidelines
Have a need for Bootstrap's brand resources? Great! We have only a few guidelines we follow, and in turn ask you to follow as well. These guidelines were inspired by MailChimp's Brand Assets.
Mark and logo
Use either the Bootstrap mark (a capital B) or the standard logo (just Bootstrap). It should always appear in Helvetica Neue Bold. Do not use the Twitter bird in association with Bootstrap.
B
B
Bootstrap
Bootstrap
Download mark
Download the Bootstrap mark in one of three styles, each available as an SVG file. Right click, Save as.
Name
The project and framework should always be referred to as Bootstrap. No Twitter before it, no capital s, and no abbreviations except for one, a capital B.
Bootstrap
(correct)
BootStrap
(incorrect)
Twitter Bootstrap
(incorrect)
Colors
Our docs and branding use a handful of primary colors to differentiate what is Bootstrap from what is in Bootstrap. In other words, if it's purple, it's representative of Bootstrap.
A list of the browser bugs that Bootstrap is currently grappling with.
Browser bugs
Bootstrap currently works around several outstanding browser bugs in major browsers to deliver the best cross-browser experience possible. Some bugs, like those listed below, cannot be solved by us.
We publicly list browser bugs that are impacting us here, in the hopes of expediting the process of fixing them. For information on Bootstrap's browser compatibility, see our browser compatibility docs.
There are several features specified in Web standards which would allow us to make Bootstrap more robust, elegant, or performant, but aren't yet implemented in certain browsers, thus preventing us from taking advantage of them.
We publicly list these "most wanted" feature requests here, in the hopes of expediting the process of getting them implemented.
A list of the browser bugs that Bootstrap is currently grappling with.
Browser bugs
Bootstrap currently works around several outstanding browser bugs in major browsers to deliver the best cross-browser experience possible. Some bugs, like those listed below, cannot be solved by us.
We publicly list browser bugs that are impacting us here, in the hopes of expediting the process of fixing them. For information on Bootstrap's browser compatibility, see our browser compatibility docs.
There are several features specified in Web standards which would allow us to make Bootstrap more robust, elegant, or performant, but aren't yet implemented in certain browsers, thus preventing us from taking advantage of them.
We publicly list these "most wanted" feature requests here, in the hopes of expediting the process of getting them implemented.
\ No newline at end of file
diff --git a/docs/3.3/components/index.html b/docs/3.3/components/index.html
index d9f4526426..3e373ccf25 100644
--- a/docs/3.3/components/index.html
+++ b/docs/3.3/components/index.html
@@ -724,4 +724,4 @@
<!-- 4:3 aspect ratio --><divclass="embed-responsive embed-responsive-4by3"><iframeclass="embed-responsive-item"src="..."></iframe>
-</div>
Wells
Default well
Use the well as a simple effect on an element to give it an inset effect.
Look, I'm in a well!
<divclass="well">...</div>
Optional classes
Control padding and rounded corners with two optional modifier classes.
Look, I'm in a large well!
<divclass="well well-lg">...</div>
Look, I'm in a small well!
<divclass="well well-sm">...</div>
\ No newline at end of file
+</div>
Wells
Default well
Use the well as a simple effect on an element to give it an inset effect.
Look, I'm in a well!
<divclass="well">...</div>
Optional classes
Control padding and rounded corners with two optional modifier classes.
Look, I'm in a large well!
<divclass="well well-lg">...</div>
Look, I'm in a small well!
<divclass="well well-sm">...</div>
\ No newline at end of file
diff --git a/docs/3.3/css/index.html b/docs/3.3/css/index.html
index c80bc596ef..0e403fc0a3 100644
--- a/docs/3.3/css/index.html
+++ b/docs/3.3/css/index.html
@@ -1104,4 +1104,4 @@ To edit settings, press <kbd><kbd>ctrl// Usage
.jumbotron{.img-retina("/img/bg-1x.png","/img/bg-2x.png",100px,100px);
-}
Using Sass
While Bootstrap is built on Less, it also has an official Sass port. We maintain it in a separate GitHub repository and handle updates with a conversion script.
What's included
Since the Sass port has a separate repo and serves a slightly different audience, the contents of the project differ greatly from the main Bootstrap project. This ensures the Sass port is as compatible with as many Sass-based systems as possible.
Path
Description
lib/
Ruby gem code (Sass configuration, Rails and Compass integrations)
For information on how to install and use Bootstrap for Sass, consult the GitHub repository readme. It's the most up to date source and includes information for use with Rails, Compass, and standard Sass projects.
While Bootstrap is built on Less, it also has an official Sass port. We maintain it in a separate GitHub repository and handle updates with a conversion script.
What's included
Since the Sass port has a separate repo and serves a slightly different audience, the contents of the project differ greatly from the main Bootstrap project. This ensures the Sass port is as compatible with as many Sass-based systems as possible.
Path
Description
lib/
Ruby gem code (Sass configuration, Rails and Compass integrations)
For information on how to install and use Bootstrap for Sass, consult the GitHub repository readme. It's the most up to date source and includes information for use with Rails, Compass, and standard Sass projects.
The less/, js/, and fonts/ are the source code for our CSS, JS, and icon fonts (respectively). The dist/ folder includes everything listed in the precompiled download section above. The docs/ folder includes the source code for our documentation, and examples/ of Bootstrap usage. Beyond that, any other included file provides support for packages, license information, and development.
Compiling CSS and JavaScript
Bootstrap uses Grunt for its build system, with convenient methods for working with the framework. It's how we compile our code, run tests, and more.
Install grunt-cli globally with npm install -g grunt-cli.
Navigate to the root /bootstrap/ directory, then run npm install. npm will look at the package.json file and automatically install the necessary local dependencies listed there.
When completed, you'll be able to run the various Grunt commands provided from the command line.
Available Grunt commands
grunt dist (Just compile CSS and JavaScript)
Regenerates the /dist/ directory with compiled and minified CSS and JavaScript files. As a Bootstrap user, this is normally the command you want.
grunt watch (Watch)
Watches the Less source files and automatically recompiles them to CSS whenever you save a change.
Builds and tests CSS, JavaScript, and other assets which are used when running the documentation locally via bundle exec jekyll serve.
grunt (Build absolutely everything and run tests)
Compiles and minifies CSS and JavaScript, builds the documentation website, runs the HTML5 validator against the docs, regenerates the Customizer assets, and more. Requires Jekyll. Usually only necessary if you're hacking on Bootstrap itself.
Troubleshooting
Should you encounter problems with installing dependencies or running Grunt commands, first delete the /node_modules/ directory generated by npm. Then, rerun npm install.
Basic template
Start with this basic HTML template, or modify these examples. We hope you'll customize our templates and examples, adapting them to suit your needs.
Copy the HTML below to begin working with a minimal Bootstrap document.
<!DOCTYPE html>
+ └── examples/
The less/, js/, and fonts/ are the source code for our CSS, JS, and icon fonts (respectively). The dist/ folder includes everything listed in the precompiled download section above. The docs/ folder includes the source code for our documentation, and examples/ of Bootstrap usage. Beyond that, any other included file provides support for packages, license information, and development.
Compiling CSS and JavaScript
Bootstrap uses Grunt for its build system, with convenient methods for working with the framework. It's how we compile our code, run tests, and more.
Install grunt-cli globally with npm install -g grunt-cli.
Navigate to the root /bootstrap/ directory, then run npm install. npm will look at the package.json file and automatically install the necessary local dependencies listed there.
When completed, you'll be able to run the various Grunt commands provided from the command line.
Available Grunt commands
grunt dist (Just compile CSS and JavaScript)
Regenerates the /dist/ directory with compiled and minified CSS and JavaScript files. As a Bootstrap user, this is normally the command you want.
grunt watch (Watch)
Watches the Less source files and automatically recompiles them to CSS whenever you save a change.
Builds and tests CSS, JavaScript, and other assets which are used when running the documentation locally via bundle exec jekyll serve.
grunt (Build absolutely everything and run tests)
Compiles and minifies CSS and JavaScript, builds the documentation website, runs the HTML5 validator against the docs, regenerates the Customizer assets, and more. Requires Jekyll. Usually only necessary if you're hacking on Bootstrap itself.
Troubleshooting
Should you encounter problems with installing dependencies or running Grunt commands, first delete the /node_modules/ directory generated by npm. Then, rerun npm install.
Basic template
Start with this basic HTML template, or modify these examples. We hope you'll customize our templates and examples, adapting them to suit your needs.
Copy the HTML below to begin working with a minimal Bootstrap document.
Build on the basic template above with Bootstrap's many components. We encourage you to customize and adapt Bootstrap to suit your individual project's needs.
Attach a footer to the bottom of the viewport when the content is shorter than it.
Sticky footer with navbar
Attach a footer to the bottom of the viewport with a fixed navbar at the top.
Experiments
Non-responsive Bootstrap
Easily disable the responsiveness of Bootstrap per our docs.
Off-canvas
Build a toggleable off-canvas navigation menu for use with Bootstrap.
Tools
Bootlint
Bootlint is the official Bootstrap HTML linter tool. It automatically checks for several common HTML mistakes in webpages that are using Bootstrap in a fairly "vanilla" way. Vanilla Bootstrap's components/widgets require their parts of the DOM to conform to certain structures. Bootlint checks that instances of Bootstrap components have correctly-structured HTML. Consider adding Bootlint to your Bootstrap web development toolchain so that none of the common mistakes slow down your project's development.
Community
Stay up to date on the development of Bootstrap and reach out to the community with these helpful resources.
Developers should use the keyword bootstrap on packages which modify or add to the functionality of Bootstrap when distributing through npm or similar delivery mechanisms for maximum discoverability.
Find inspiring examples of people building with Bootstrap at the Bootstrap Expo.
Bootstrap automatically adapts your pages for various screen sizes. Here's how to disable this feature so your page works like this non-responsive example.
Steps to disable page responsiveness
Omit the viewport <meta> mentioned in the CSS docs
Override the width on the .container for each grid tier with a single width, for example width: 970px !important; Be sure that this comes after the default Bootstrap CSS. You can optionally avoid the !important with media queries or some selector-fu.
If using navbars, remove all navbar collapsing and expanding behavior.
For grid layouts, use .col-xs-* classes in addition to, or in place of, the medium/large ones. Don't worry, the extra-small device grid scales to all resolutions.
You'll still need Respond.js for IE8 (since our media queries are still there and need to be processed). This disables the "mobile site" aspects of Bootstrap.
Bootstrap template with responsiveness disabled
We've applied these steps to an example. Read its source code to see the specific changes implemented.
Looking to migrate from an older version of Bootstrap to v3.x? Check out our migration guide.
Browser and device support
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
Specifically, we support the latest versions of the following browsers and platforms.
Alternative browsers which use the latest version of WebKit, Blink, or Gecko, whether directly or via the platform's web view API, are not explicitly supported. However, Bootstrap should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below.
Mobile devices
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.
Chrome
Firefox
Safari
Android
Supported
Supported
N/A
iOS
Supported
Supported
Supported
Desktop browsers
Similarly, the latest versions of most desktop browsers are supported.
Chrome
Firefox
Internet Explorer
Opera
Safari
Mac
Supported
Supported
N/A
Supported
Supported
Windows
Supported
Supported
Supported
Supported
Not supported
On Windows, we support Internet Explorer 8-11.
For Firefox, in addition to the latest normal stable release, we also support the latest Extended Support Release (ESR) version of Firefox.
Unofficially, Bootstrap should look and behave well enough in Chromium and Chrome for Linux, Firefox for Linux, and Internet Explorer 7, as well as Microsoft Edge, 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.
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.
Feature
Internet Explorer 8
Internet Explorer 9
border-radius
Not supported
Supported
box-shadow
Not supported
Supported
transform
Not supported
Supported, with -ms prefix
transition
Not supported
placeholder
Not supported
Visit Can I use... for details on browser support of CSS3 and HTML5 features.
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.
Respond.js and file://
Due to browser security rules, Respond.js doesn't work with pages viewed via the file:// protocol (like when opening a local HTML file). To test responsive features in IE8, view your pages over HTTP(S). See the Respond.js docs for details.
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
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.
Internet Explorer 8 and @font-face
IE8 has some issues with @font-face when combined with :before. Bootstrap uses that combination with its Glyphicons. If a page is cached, and loaded without the mouse over the window (i.e. hit the refresh button or load something in an iframe) then the page gets rendered before the font loads. Hovering over the page (body) will show some of the icons and hovering over the remaining icons will show those as well. See issue #13863 for details.
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:
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.
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:
@-ms-viewport{width:device-width;}
However, this doesn't work for devices running Windows Phone 8 versions older than Update 3 (a.k.a. GDR3), as it causes such devices to show a mostly desktop view instead of narrow "phone" view. To address this, you'll need to include the following CSS and JavaScript to work around the bug.
// Copyright 2014-2015 Twitter, Inc.
-// Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
+// Licensed under MIT (https://github.com/twbs/bootstrap/blob/main/LICENSE)if(navigator.userAgent.match(/IEMobile\/10\.0/)){varmsViewportStyle=document.createElement('style')msViewportStyle.appendChild(
@@ -129,4 +129,4 @@
<divclass="container"id="content"tabindex="-1"><!-- The main page content --></div>
-</body>
Nested headings
When nesting headings (<h1> - <h6>), your primary document header should be an <h1>. Subsequent headings should make logical use of <h2> - <h6> such that screen readers can construct a table of contents for your pages.
Currently, some of the default color combinations available in Bootstrap (such as the various styled button classes, some of the code highlighting colors used for basic code blocks, the .bg-primarycontextual background helper class, and the default link color when used on a white background) have a low contrast ratio (below the recommended ratio of 4.5:1). This can cause problems to users with low vision or who are color blind. These default colors may need to be modified to increase their contrast and legibility.
Bootstrap is released under the MIT license and is copyright 2016 Twitter. Boiled down to smaller chunks, it can be described with the following conditions.
It requires you to:
Keep the license and copyright notice included in Bootstrap's CSS and JavaScript files when you use them in your works
It permits you to:
Freely download and use Bootstrap, in whole or in part, for personal, private, company internal, or commercial purposes
Use Bootstrap in packages or distributions that you create
Modify the source code
Grant a sublicense to modify and distribute Bootstrap to third parties not included in the license
It forbids you to:
Hold the authors and license owners liable for damages as Bootstrap is provided without warranty
Hold the creators or copyright holders of Bootstrap liable
Redistribute any piece of Bootstrap without proper attribution
Use any marks owned by Twitter in any way that might state or imply that Twitter endorses your distribution
Use any marks owned by Twitter in any way that might state or imply that you created the Twitter software in question
It does not require you to:
Include the source of Bootstrap itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it
Submit changes that you make to Bootstrap back to the Bootstrap project (though such feedback is encouraged)
Community members have translated Bootstrap's documentation into various languages. None are officially supported and they may not always be up to date.
We don't help organize or host translations, we just link to them.
Finished a new or better translation? Open a pull request to add it to our list.
\ No newline at end of file
+</body>
Nested headings
When nesting headings (<h1> - <h6>), your primary document header should be an <h1>. Subsequent headings should make logical use of <h2> - <h6> such that screen readers can construct a table of contents for your pages.
Currently, some of the default color combinations available in Bootstrap (such as the various styled button classes, some of the code highlighting colors used for basic code blocks, the .bg-primarycontextual background helper class, and the default link color when used on a white background) have a low contrast ratio (below the recommended ratio of 4.5:1). This can cause problems to users with low vision or who are color blind. These default colors may need to be modified to increase their contrast and legibility.
Bootstrap is released under the MIT license and is copyright 2016 Twitter. Boiled down to smaller chunks, it can be described with the following conditions.
It requires you to:
Keep the license and copyright notice included in Bootstrap's CSS and JavaScript files when you use them in your works
It permits you to:
Freely download and use Bootstrap, in whole or in part, for personal, private, company internal, or commercial purposes
Use Bootstrap in packages or distributions that you create
Modify the source code
Grant a sublicense to modify and distribute Bootstrap to third parties not included in the license
It forbids you to:
Hold the authors and license owners liable for damages as Bootstrap is provided without warranty
Hold the creators or copyright holders of Bootstrap liable
Redistribute any piece of Bootstrap without proper attribution
Use any marks owned by Twitter in any way that might state or imply that Twitter endorses your distribution
Use any marks owned by Twitter in any way that might state or imply that you created the Twitter software in question
It does not require you to:
Include the source of Bootstrap itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it
Submit changes that you make to Bootstrap back to the Bootstrap project (though such feedback is encouraged)
Community members have translated Bootstrap's documentation into various languages. None are officially supported and they may not always be up to date.
We don't help organize or host translations, we just link to them.
Finished a new or better translation? Open a pull request to add it to our list.
\ No newline at end of file
diff --git a/docs/3.3/index.html b/docs/3.3/index.html
index 6e338d0fcc..216e53bf9b 100644
--- a/docs/3.3/index.html
+++ b/docs/3.3/index.html
@@ -130,7 +130,7 @@
diff --git a/docs/3.3/javascript/index.html b/docs/3.3/javascript/index.html
index 3e942ea79a..58c4bbdf1a 100644
--- a/docs/3.3/javascript/index.html
+++ b/docs/3.3/javascript/index.html
@@ -405,4 +405,4 @@ sagittis lacus vel augue laoreet rutrum faucibus.">}})
Options
Options can be passed via data attributes or JavaScript. For data attributes, append the option name to data-, as in data-offset-top="200".
Name
type
default
description
offset
number | function | object
10
Pixels to offset from screen when calculating position of scroll. If a single number is provided, the offset will be applied in both top and bottom directions. To provide a unique, bottom and top offset just provide an object offset: { top: 10 } or offset: { top: 10, bottom: 5 }. Use a function when you need to dynamically calculate an offset.
target
selector | node | jQuery element
the window object
Specifies the target element of the affix.
Methods
.affix(options)
Activates your content as affixed content. Accepts an optional options object.
$('#myAffix').affix({offset:15
-})
.affix('checkPosition')
Recalculates the state of the affix based on the dimensions, position, and scroll position of the relevant elements. The .affix, .affix-top, and .affix-bottom classes are added to or removed from the affixed content according to the new state. This method needs to be called whenever the dimensions of the affixed content or the target element are changed, to ensure correct positioning of the affixed content.
$('#myAffix').affix('checkPosition')
Events
Bootstrap's affix plugin exposes a few events for hooking into affix functionality.
Event Type
Description
affix.bs.affix
This event fires immediately before the element has been affixed.
affixed.bs.affix
This event is fired after the element has been affixed.
affix-top.bs.affix
This event fires immediately before the element has been affixed-top.
affixed-top.bs.affix
This event is fired after the element has been affixed-top.
affix-bottom.bs.affix
This event fires immediately before the element has been affixed-bottom.
affixed-bottom.bs.affix
This event is fired after the element has been affixed-bottom.
\ No newline at end of file
+})
.affix('checkPosition')
Recalculates the state of the affix based on the dimensions, position, and scroll position of the relevant elements. The .affix, .affix-top, and .affix-bottom classes are added to or removed from the affixed content according to the new state. This method needs to be called whenever the dimensions of the affixed content or the target element are changed, to ensure correct positioning of the affixed content.
$('#myAffix').affix('checkPosition')
Events
Bootstrap's affix plugin exposes a few events for hooking into affix functionality.
Event Type
Description
affix.bs.affix
This event fires immediately before the element has been affixed.
affixed.bs.affix
This event is fired after the element has been affixed.
affix-top.bs.affix
This event fires immediately before the element has been affixed-top.
affixed-top.bs.affix
This event is fired after the element has been affixed-top.
affix-bottom.bs.affix
This event fires immediately before the element has been affixed-bottom.
affixed-bottom.bs.affix
This event is fired after the element has been affixed-bottom.
\ No newline at end of file
diff --git a/docs/3.3/migration/index.html b/docs/3.3/migration/index.html
index 4dbeeb6dd4..8cf56a9186 100644
--- a/docs/3.3/migration/index.html
+++ b/docs/3.3/migration/index.html
@@ -1 +1 @@
- Migrating to v3.x · Bootstrap
Guidance on how to upgrade from Bootstrap v2.x to v3.x with emphasis on major changes, what's new, and what's been removed.
Migrating from 2.x to 3.0
Bootstrap 3 is not backwards compatible with v2.x. Use this section as a general guide to upgrading from v2.x to v3.0. For a broader overview, see what's new in the v3.0 release announcement.
Major class changes
This table shows the style changes between v2.x and v3.0.
Other changes in v3.0 are not immediately apparent. Base classes, key styles, and behaviors have been adjusted for flexibility and our mobile first approach. Here's a partial list:
By default, text-based form controls now receive only minimal styling. For focus colors and rounded corners, apply the .form-control class on the element to style.
Text-based form controls with the .form-control class applied are now 100% wide by default. Wrap inputs inside <div class="col-*"></div> to control input widths.
.badge no longer has contextual (-success,-primary,etc..) classes.
.btn must also use .btn-default to get the "default" button.
.row is now fluid.
Images are no longer responsive by default. Use .img-responsive for fluid <img> size.
The icons, now .glyphicon, are now font based. Icons also require a base and icon class (e.g. .glyphicon .glyphicon-asterisk).
Modal markup has changed significantly. The .modal-header, .modal-body, and .modal-footer sections are now wrapped in .modal-content and .modal-dialog for better mobile styling and behavior. Also, you should no longer apply .hide to .modal in your markup.
As of v3.1.0, the HTML loaded by the remote modal option is now injected into the .modal-content (from v3.0.0 to v3.0.3, into the .modal) instead of into the .modal-body. This allows you to also easily vary the header and footer of the modal, not just the modal body.
The checkbox and radio features of the button.js plugin now both use data-toggle="buttons" instead of data-toggle="buttons-checkbox" or data-toggle="buttons-radio" in their markup.
JavaScript events are namespaced. For example, to handle the modal "show" event, use 'show.bs.modal'. For tabs "shown" use 'shown.bs.tab', etc.
For more information on upgrading to v3.0, and code snippets from the community, see Bootply.
\ No newline at end of file
+ Migrating to v3.x · Bootstrap
Guidance on how to upgrade from Bootstrap v2.x to v3.x with emphasis on major changes, what's new, and what's been removed.
Migrating from 2.x to 3.0
Bootstrap 3 is not backwards compatible with v2.x. Use this section as a general guide to upgrading from v2.x to v3.0. For a broader overview, see what's new in the v3.0 release announcement.
Major class changes
This table shows the style changes between v2.x and v3.0.
Other changes in v3.0 are not immediately apparent. Base classes, key styles, and behaviors have been adjusted for flexibility and our mobile first approach. Here's a partial list:
By default, text-based form controls now receive only minimal styling. For focus colors and rounded corners, apply the .form-control class on the element to style.
Text-based form controls with the .form-control class applied are now 100% wide by default. Wrap inputs inside <div class="col-*"></div> to control input widths.
.badge no longer has contextual (-success,-primary,etc..) classes.
.btn must also use .btn-default to get the "default" button.
.row is now fluid.
Images are no longer responsive by default. Use .img-responsive for fluid <img> size.
The icons, now .glyphicon, are now font based. Icons also require a base and icon class (e.g. .glyphicon .glyphicon-asterisk).
Modal markup has changed significantly. The .modal-header, .modal-body, and .modal-footer sections are now wrapped in .modal-content and .modal-dialog for better mobile styling and behavior. Also, you should no longer apply .hide to .modal in your markup.
As of v3.1.0, the HTML loaded by the remote modal option is now injected into the .modal-content (from v3.0.0 to v3.0.3, into the .modal) instead of into the .modal-body. This allows you to also easily vary the header and footer of the modal, not just the modal body.
The checkbox and radio features of the button.js plugin now both use data-toggle="buttons" instead of data-toggle="buttons-checkbox" or data-toggle="buttons-radio" in their markup.
JavaScript events are namespaced. For example, to handle the modal "show" event, use 'show.bs.modal'. For tabs "shown" use 'shown.bs.tab', etc.
For more information on upgrading to v3.0, and code snippets from the community, see Bootply.
\ No newline at end of file
diff --git a/docs/4.0/examples/index.html b/docs/4.0/examples/index.html
index 6648d0864c..a84b39adca 100644
--- a/docs/4.0/examples/index.html
+++ b/docs/4.0/examples/index.html
@@ -377,7 +377,7 @@
Mark Otto @mdo 
Jacob Thornton @fat 
Chris Rebert @cvrebert 
Julian Thilo @juthilo 
XhmikosR @xhmikosr 
Heinrich Fenkart @hnrch02 
Patrick H. Lauke @patrickhlauke 
Thomas McDonald @thomas-mcdonald 
Gleb Mazovetskiy @glebm 
