aboutsummaryrefslogtreecommitdiff
path: root/js/tests/unit/carousel.js
AgeCommit message (Collapse)AuthorFilesLines
2019-07-23rewrite carousel unit testsJohann-S1-1370/+0
2019-03-27Reset carousel touch delta x to prevent click transformation in swipe (#28558)Johann-S1-2/+4
2019-03-11Comply to the new rules.XhmikosR1-7/+11
2019-02-27tests: add tests for plugins version. (#28366)XhmikosR1-2/+1
2019-02-20bump to 4.2.1Johann-S1-2/+2
2019-02-20chore(update): bump to 4.1.3Johann-S1-11/+14
2019-02-20fix(unit-test): dropdown, collapse and carouselJohann-S1-2/+2
2019-02-20fix(event-handler): remove the use of our event handler in unit testJohann-S1-118/+133
2019-02-20fix(data): do not use data object in our unit testsJohann-S1-4/+4
2019-02-20Rewritten modal without jquery (#23955)Alessandro Chitolina1-26/+10
* Trigger jquery events if available in event handler * Rewritten modal without jquery
2019-02-20Rewrite carousel without jqueryJohann-S1-92/+122
2019-01-14Fix Carousel's touch option to not add touch listeners when set to false ↵Johann-S1-2/+15
(#28046)
2019-01-04carousel should not cycle when there is no data-ride on init (#27968)Johann-S1-0/+47
2018-10-29add unit tests for our carouselJohann-S1-0/+44
2018-10-20avoid drag imgJohann-S1-9/+11
2018-10-20Set touch-action to "none"patrickhlauke1-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-20Use correct touch-action valuespatrickhlauke1-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-20use pointer events if availableJohann-S1-3/+122
2018-10-20swipe left/right without hammerjsJohann-S1-42/+31
2018-10-20Add touch support in our carousel with HammerJS.Johann-S1-0/+127
2018-09-18feature(carousel): carousel-item interval (#26667)Christopher Morrissey1-0/+48
adds the ability to assign data-interval to an individual carousel-item
2018-05-22chore(deps): update qunit and karma-qunitJohann-S1-0/+1
2018-01-11Comply to the new rules.XhmikosR1-438/+460
2017-11-09Use native pseudo-selectors instead of jQuery selectors (#24713)Vasilii Artemchuk1-6/+6
2017-08-23Tweak ESLint rules.XhmikosR1-5/+5
2017-08-17Add a unit test to check if the carousel do not cycle when its parent isn't ↵Johann-S1-0/+39
visible
2017-08-17Unit test to check if our carousel do not cycle when we cannot see itJohann-S1-0/+37
2017-04-17Fix carousel "hover" behavior on touch-enabled devicesPatrick H. Lauke1-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-22Carousel - Add attributes from and to for Slid and Slide events (#21668)Johann1-0/+43
Carousel - Add attributes from and to for Slid and Slide events
2016-12-23Carousel: Only prevents default for ARROW_LEFT and ARROW_RIGHT keysMatheus Azzi1-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-26Merge pull request #19058 from Johann-S/carouselInputMark Otto1-0/+32
Carousel - Do not prevent on keydown for input and textarea
2016-11-24Make JS compliant with the new ESLint rules.Bardi Harborow1-1/+1
2016-02-01Carousel - Do not prevent on keydown for input and textareaJohann-S1-0/+32
2015-10-02Add throw error for undefined method on pluginsJohann-S1-0/+12
2015-05-13al tests passing, dist rebuilt, w/typecheckerfat1-1/+3
2015-05-13add simple type checker implementationfat1-0/+30
2015-05-07carousel -> es6fat1-80/+80
2015-05-06remove closureness from pluginsfat1-140/+160
2015-02-11bootstrap onto closurefat1-4/+5
2015-01-21Merge branch 'master' into v4Chris Rebert1-27/+27
2015-01-20update JS unit tests to future-proof QUnit 1.16.0 APIChris Rebert1-27/+27
[skip validator]
2014-12-17rename .item => .carousel-itemChris Rebert1-76/+76
2014-11-15add unit tests for Carousel's 'wrap' optionChris Rebert1-0/+153
2014-11-04Have Carousel ignore keyboard events from <input>s or <textarea>s; fixes #14991Chris Rebert1-0/+42
2014-10-03Add `keyboard` option to carouselHeinrich Fenkart1-0/+79
Also adds unit tests for keyboard events. Fixes #14468.
2014-09-23Only enable `pause: hover` for non-touch browsersHeinrich Fenkart1-0/+22
Fixes #11967.
2014-07-31Fix #13818 by using more robust "find next carousel item" logicChris Rebert1-1/+26
Also adds another test for #9461: carousel next/prev should ignore non-items
2014-07-06Move to leading plusesHeinrich Fenkart1-198/+198
2014-07-06Clean carousel unit tests upHeinrich Fenkart1-90/+292
2014-06-06Comply to the new style.XhmikosR1-2/+3