- 14 May, 2017 1 commit
-
-
Johann-S authored
-
- 26 Apr, 2017 1 commit
-
-
Anna authored
-
- 25 Apr, 2017 1 commit
-
-
Pierre Vanduynslager authored
-
- 20 Apr, 2017 1 commit
-
-
Bardi Harborow authored
-
- 17 Apr, 2017 1 commit
-
-
Patrick H. Lauke authored
* Add carousel mouse listeners even if touch events enabled - touch events are enabled not just on "mobile", just also on touch-enabled desktop/laptop devices; additionally, it's possible to pair a mouse with traditionally touch-only devices (e.g. Android phones/tablets); currently, in these situations the carousel WON'T pause even when using a mouse * Restart cycle after touchend as `mouseenter` is fired as part of the touch compatibility events, the previous change results in carousels which cycle until the user tapped/interacted with them. after that they stop cycling (as `mouseleave` is not sent to the carousel after user scrolled/tapped away). this fix resets the cycling after `touchend` - essentially returning to the previous behavior, where on touch the carousel essentially never pauses, but now with the previous fix it at least pauses correctly for mouse users on touch-enabled devices. includes documentation for this new behavior.
-
- 10 Apr, 2017 2 commits
-
-
Patrick H. Lauke authored
* Remove aria-expanded from collapse.js target element aria-expanded="true"/aria-expanded="false" only applies to the trigger, not the element that is being expanded/collapsed. * Tweak collapse.js accessibility section ...to make it clearer that the aria-expanded attribute always just goes on the control. * Fix collapse.js unit tests - reword some of the text to make it clear we're checking behavior of trigger/control - move incorrect aria-expanded out of the <div>s and to the actual trigger/control <a>s - fix incorrect test assertion text output false -> true
-
Patrick H. Lauke authored
* Only change aria-pressed if it's not an input-based radio or checkbox group aria-pressed="true"/aria-pressed="false" is really only useful for making on/off toggles out of, say, `<button>` elements. the attribute is useless (and potentially confusing/conflicting) on, say, `<label>` elements for an existing `<input type="radio">` or similar. * Add unit test for buttons.js and radio/checkbox inputs in button groups
-
- 03 Apr, 2017 1 commit
-
-
Ilias authored
-
- 02 Apr, 2017 2 commits
-
-
Ilias authored
-
Pierre Vanduynslager authored
-
- 31 Mar, 2017 1 commit
-
-
Johann-S authored
-
- 28 Mar, 2017 2 commits
- 27 Mar, 2017 1 commit
-
-
Johann authored
-
- 23 Mar, 2017 1 commit
-
-
Pierre Vanduynslager authored
Fix accordion behavior with JQuery interface
-
- 22 Mar, 2017 1 commit
-
-
Johann authored
Carousel - Add attributes from and to for Slid and Slide events
-
- 21 Mar, 2017 1 commit
-
-
Pierre Vanduynslager authored
-
- 18 Mar, 2017 1 commit
-
-
Johann authored
* Allow to use Tab.js with list-group * Allow to use list-group with div parent instead of an ul parent
-
- 09 Mar, 2017 1 commit
-
-
Johann-S authored
-
- 08 Feb, 2017 1 commit
-
-
Pierre-Denis Vanduynslager authored
-
- 21 Jan, 2017 4 commits
-
-
Pierre-Denis Vanduynslager authored
-
Pierre-Denis Vanduynslager authored
-
Pierre-Denis Vanduynslager authored
-
Pierre-Denis Vanduynslager authored
-
- 06 Jan, 2017 1 commit
-
-
Pierre-Denis Vanduynslager authored
-
- 04 Jan, 2017 1 commit
-
-
Johann-S authored
-
- 02 Jan, 2017 2 commits
-
-
Pierre-Denis Vanduynslager authored
* Close dropdown menu when focusing an outside element * Update unit test to new markup
-
Mark Otto authored
-
- 31 Dec, 2016 1 commit
-
-
Johann-S authored
-
- 29 Dec, 2016 1 commit
-
-
Johann-S authored
-
- 27 Dec, 2016 1 commit
-
-
Max Beatty authored
-
- 25 Dec, 2016 1 commit
-
-
Alessandro Rodi authored
* [Fix #19849] Tabs are opened even if disabled. * fix hund code review hints * rollback hound issues because Travis fails
-
- 23 Dec, 2016 1 commit
-
-
Matheus Azzi authored
Fixes 2 bugs: 1. All keydowns were being prevented. Because of that the user wasn't able to navigate in the whole page using ARROW_UP/ARROW_DOWN. 2. Even when is an input or textarea the keydowns were being prevented. Because of that the user wasn't able to type any text on these elements.
-
- 08 Dec, 2016 1 commit
-
-
Starsam80 authored
-
- 28 Nov, 2016 1 commit
-
-
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.
-
- 26 Nov, 2016 1 commit
-
-
Johann authored
-
- 25 Nov, 2016 1 commit
-
-
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 1 commit
-
-
Bardi Harborow authored
-
- 01 Nov, 2016 1 commit
-
-
Johann authored
-
- 25 Oct, 2016 1 commit
-
-
Johann-S authored
-