bootstrap - The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.

Age	Commit message (Collapse)	Author	Files	Lines
2018-12-21	Prep for v4.2.0 release	Mark Otto	1	-357/+0
	- Move 4.1 docs to 4.2 - Update versions everywhere to 4.1.3 with release script - Manually bump the shorthand version in package.json - Add 4.2 to the versions docs page - Update some redirects - Fix tests asset URLs - Bump Nuget and more
2018-12-05	Allow Tooltips/Popovers to work in shadow DOM	Johann-S	1	-0/+1

2018-11-28	Revert "Use `h5` for callouts so that they are not included in ToC."	XhmikosR	1	-1/+1
	This reverts commit 11da1601140174e4fa4e0e25e7f66fc21c08e927. This is no longer needed with jekyll-toc 0.9.1.
2018-11-27	Use `h5` for callouts so that they are not included in ToC.	XhmikosR	1	-1/+1
	Callouts are already excluded from ToC, but due to a limitation in jekyll-toc they are still being included. We should revisit this if the bug is fixed later.
2018-11-03	Add Sass variable for prefers-reduced-motion, add callout to affected ↵	Patrick H. Lauke	1	-0/+2
	components (#27581) * Tweak the accessibility/reduced motion text include mention of carousel slides, remove the (now inaccurate, as Firefox 63 includes it too) mention that support is limited to Safari/macOS xref https://github.com/twbs/bootstrap/issues/27525 * Add new callout for reduced motion * Add variable to control prefers-reduced-motion media query support * Add callout about prefers-reduced-motion to all components currently using animation which are affected
2018-11-01	Make meaning of tooltip's `selector` option clearer (#27573)	Sebastian Hädrich	1	-1/+1

2018-08-02	Fix #26990 broken external example	Mitchell Grice	1	-1/+1

2018-07-20	Merge branch 'document-tooltip-flickering' of ↵	Mark Otto	1	-0/+11
	https://github.com/simPod/bootstrap into simPod-document-tooltip-flickering
2018-07-11	Reorganize docs for easier deploys	Mark Otto	1	-0/+343
	With the current docs directory setup, I'm making too many mistakes and have to manually address path changes and directory moves on deploy. This makes for a frustrating experience developing locally and shipping releases. With this PR, we're basically back to the same setup from v3—duplicating the dist directory into our docs directory. Not the most ideal, but very straightforward for me as the release manager.