- 20 Dec, 2016 1 commit
-
-
Mark Otto authored
-
- 08 Dec, 2016 3 commits
- 05 Dec, 2016 3 commits
- 02 Dec, 2016 2 commits
- 30 Nov, 2016 1 commit
-
-
Mark Otto authored
-
- 29 Nov, 2016 2 commits
-
-
Bardi Harborow authored
-
Mark Otto authored
-
- 28 Nov, 2016 3 commits
-
-
Juno_okyo authored
-
Mark Otto authored
-
Rob Ruana authored
When the rubberband effect causes Safari to scroll past the top of the page, the value of scrollTop becomes negative. If the offset of the first ScrollSpy target is 0 - essentially if the target is at the top of the page - then ScrollSpy should not clear the active item. Conceptually, the first item should remain active when rubberbanding past the top of the page. This commit fixes issue #21055 by verifying the first scrollspy target is not at the top of the page before clearing the active nav-item.
-
- 27 Nov, 2016 1 commit
-
-
Mark Otto authored
-
- 26 Nov, 2016 10 commits
-
-
Mark Otto authored
-
Mark Otto authored
-
Mark Otto authored
See https://travis-ci.org/twbs/bootstrap/jobs/179010884 for build failure
-
Mark Otto authored
-
Mark Otto authored
-
Pierre-Denis Vanduynslager authored
Dropdown perf - on keyboard nav, find active item in the active dropdown rather than the whole document (#19953)
-
andyexeter authored
-
Johann authored
-
matus authored
-
matus authored
-
- 25 Nov, 2016 2 commits
-
-
Mark Otto authored
-
Matt Hernandez authored
* Fix bug with dropdown tab links not deactivating when other tab or dropdown link is clicked * Revise bug fix for more stability
-
- 24 Nov, 2016 2 commits
-
-
Bardi Harborow authored
-
Bardi Harborow authored
-
- 12 Nov, 2016 1 commit
-
-
Bardi Harborow authored
-
- 01 Nov, 2016 5 commits
-
-
Mark Otto authored
-
Mark Otto authored
* Explore responsive display utils, but with a twist: lowest breakpoint has no breakpoint modifier in the class name * make floats use the same format, add float-none mixin
-
Mark Otto authored
-
Johann authored
-
Bardi Harborow authored
-
- 30 Oct, 2016 2 commits
-
-
Mark Otto authored
-
Ilias authored
* Fix #17964 Some browsers are lazy when updating dom elements after transition effects. This can be fixed by reading element properties such as offsetHeight or offsetWidth. However, creating a function using the Function constructor just to access such element, results in a violation of Content Security Policy (where applied), which in turn crashes the application. This fix actually reverts to the way this was handled in v3 and should work as intended.
-
- 27 Oct, 2016 1 commit
-
-
Mark Otto authored
-
- 25 Oct, 2016 1 commit
-
-
Johann-S authored
-