aboutsummaryrefslogtreecommitdiffstats
path: root/src/ngScenario/browserTrigger.js
AgeCommit message (Collapse)Author
2013-10-22style: make jshint happyVojta Jina
2013-09-26feat(browserTrigger): allow support for custom timeStamps in eventsMatias Niemelä
2013-09-07fix(browserTrigger): do not use document.createEvent methodPete Bacon Darwin
Firefox 23 has deprecated the use of createEvent for transition and animation events. We must now use `new TransitionEvent()` and `new AnimationEvent()` if they are available. But of course IE doesn't support this format correctly so we must wrap the attempt in a try block and revert to document.createEvent if necessary..
2013-09-06fix(ngScenario): provide event parameters as objectMatias Niemelä
BREAKING CHANGE: browserTrigger now uses an eventData object instead of direct parameters for mouse events. To migrate, place the `keys`,`x` and `y` parameters inside of an object and place that as the third parameter for the browserTrigger function.
2013-04-18test(modules): fix module tests which got disabled by ngMobileIgor Minar
When ngMobile was merged in, we accidentaly included angular-scenario.js in the test file set for modules. Loading this file overrode jasmine's `it` and `describe` global functions which essentially disabled all of ~200 unit tests for wrapped modules. This change refactors the code to run the wrapped module tests. I had to extract browserTrigger from scenario runner in order to achieve this without code duplication.