| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2021-09-15 | tests: comply to the new rules | XhmikosR | 1 | -45/+45 | |
| Use `assert.strictEqual`/`assert.true`/`assert.false` | |||||
| 2020-11-12 | Check for data-interval on the first slide of carousel - v4 (#31820) | Mitchell Bryson | 1 | -1/+14 | |
| When starting a cycle for a carousel, it only checks for a default interval, and not an interval defined on the slide element via data props. This adds a check in before creating the interval to move to the next slide. Co-authored-by: XhmikosR <[email protected]> | |||||
| 2020-09-10 | Comply to the new rules | XhmikosR | 1 | -7/+7 | |
| 2020-04-17 | Fix tests for jQuery v3.5.0. | XhmikosR | 1 | -17/+17 | |
| 2019-03-27 | Reset carousel touch delta x to prevent click transformation in swipe (#28558) | Johann-S | 1 | -2/+4 | |
| 2019-01-14 | Fix Carousel's touch option to not add touch listeners when set to false ↵ | Johann-S | 1 | -2/+15 | |
| (#28046) | |||||
| 2019-01-04 | carousel should not cycle when there is no data-ride on init (#27968) | Johann-S | 1 | -0/+47 | |
| 2018-10-29 | add unit tests for our carousel | Johann-S | 1 | -0/+44 | |
| 2018-10-20 | avoid drag img | Johann-S | 1 | -9/+11 | |
| 2018-10-20 | Set touch-action to "none" | patrickhlauke | 1 | -1/+1 | |
| Firefox currently seems extremely fickle - with `pan-y` if fires pointercancel as soon as a touch strays even a pixel or so vertically. While `touch-action: pan-y` would be ideal (allowing users to scroll the page even when their finger started the scroll on the carousel), this prevents a swipe that isn't perfectly/only horizontal to be recognised by Firefox. | |||||
| 2018-10-20 | Use correct touch-action values | patrickhlauke | 1 | -1/+1 | |
| - my fault, my original advice of using `touch-action: pan-x` is exactly the value we *don't* want to have the browser handle... | |||||
| 2018-10-20 | use pointer events if available | Johann-S | 1 | -3/+122 | |
| 2018-10-20 | swipe left/right without hammerjs | Johann-S | 1 | -42/+31 | |
| 2018-10-20 | Add touch support in our carousel with HammerJS. | Johann-S | 1 | -0/+127 | |
| 2018-09-18 | feature(carousel): carousel-item interval (#26667) | Christopher Morrissey | 1 | -0/+48 | |
| adds the ability to assign data-interval to an individual carousel-item | |||||
| 2018-05-22 | chore(deps): update qunit and karma-qunit | Johann-S | 1 | -0/+1 | |
| 2018-01-11 | Comply to the new rules. | XhmikosR | 1 | -438/+460 | |
| 2017-11-09 | Use native pseudo-selectors instead of jQuery selectors (#24713) | Vasilii Artemchuk | 1 | -6/+6 | |
| 2017-08-23 | Tweak ESLint rules. | XhmikosR | 1 | -5/+5 | |
| 2017-08-17 | Add a unit test to check if the carousel do not cycle when its parent isn't ↵ | Johann-S | 1 | -0/+39 | |
| visible | |||||
| 2017-08-17 | Unit test to check if our carousel do not cycle when we cannot see it | Johann-S | 1 | -0/+37 | |
| 2017-04-17 | Fix carousel "hover" behavior on touch-enabled devices | Patrick H. Lauke | 1 | -23/+0 | |
| * 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. | |||||
| 2017-03-22 | Carousel - Add attributes from and to for Slid and Slide events (#21668) | Johann | 1 | -0/+43 | |
| Carousel - Add attributes from and to for Slid and Slide events | |||||
| 2016-12-23 | Carousel: Only prevents default for ARROW_LEFT and ARROW_RIGHT keys | Matheus Azzi | 1 | -0/+31 | |
| 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. | |||||
| 2016-11-26 | Merge pull request #19058 from Johann-S/carouselInput | Mark Otto | 1 | -0/+32 | |
| Carousel - Do not prevent on keydown for input and textarea | |||||
| 2016-11-24 | Make JS compliant with the new ESLint rules. | Bardi Harborow | 1 | -1/+1 | |
| 2016-02-01 | Carousel - Do not prevent on keydown for input and textarea | Johann-S | 1 | -0/+32 | |
| 2015-10-02 | Add throw error for undefined method on plugins | Johann-S | 1 | -0/+12 | |
| 2015-05-13 | al tests passing, dist rebuilt, w/typechecker | fat | 1 | -1/+3 | |
| 2015-05-13 | add simple type checker implementation | fat | 1 | -0/+30 | |
| 2015-05-07 | carousel -> es6 | fat | 1 | -80/+80 | |
| 2015-05-06 | remove closureness from plugins | fat | 1 | -140/+160 | |
| 2015-02-11 | bootstrap onto closure | fat | 1 | -4/+5 | |
| 2015-01-21 | Merge branch 'master' into v4 | Chris Rebert | 1 | -27/+27 | |
| 2015-01-20 | update JS unit tests to future-proof QUnit 1.16.0 API | Chris Rebert | 1 | -27/+27 | |
| [skip validator] | |||||
| 2014-12-17 | rename .item => .carousel-item | Chris Rebert | 1 | -76/+76 | |
| 2014-11-15 | add unit tests for Carousel's 'wrap' option | Chris Rebert | 1 | -0/+153 | |
| 2014-11-04 | Have Carousel ignore keyboard events from <input>s or <textarea>s; fixes #14991 | Chris Rebert | 1 | -0/+42 | |
| 2014-10-03 | Add `keyboard` option to carousel | Heinrich Fenkart | 1 | -0/+79 | |
| Also adds unit tests for keyboard events. Fixes #14468. | |||||
| 2014-09-23 | Only enable `pause: hover` for non-touch browsers | Heinrich Fenkart | 1 | -0/+22 | |
| Fixes #11967. | |||||
| 2014-07-31 | Fix #13818 by using more robust "find next carousel item" logic | Chris Rebert | 1 | -1/+26 | |
| Also adds another test for #9461: carousel next/prev should ignore non-items | |||||
| 2014-07-06 | Move to leading pluses | Heinrich Fenkart | 1 | -198/+198 | |
| 2014-07-06 | Clean carousel unit tests up | Heinrich Fenkart | 1 | -90/+292 | |
| 2014-06-06 | Comply to the new style. | XhmikosR | 1 | -2/+3 | |
| 2014-05-01 | make new Carousel tests compatible with noConflict mode | Chris Rebert | 1 | -2/+2 | |
| 2014-04-30 | Merge pull request #11966 from colllin/noconflict | Mark Otto | 1 | -16/+25 | |
| Fix #11464 - JS noConflict() mode not working in 3.0.x | |||||
| 2014-04-21 | #11464 - Fix JS noConflict mode - Refactor all plugins to use an internal ↵ | Collin Donahue-Oponski | 1 | -16/+25 | |
| reference to the jQuery plugin, because in noConflict mode you can never expect to be defined on the jQuery object | |||||
| 2014-04-21 | add unit tests for Carousel slid events | Chris Rebert | 1 | -0/+26 | |
| 2014-04-21 | spelling fixes in Carousel unit tests | Chris Rebert | 1 | -3/+3 | |
| 2014-03-24 | fixes #9461 - Make carousel ignore non-items in carousel-inner | fat | 1 | -0/+28 | |
