aboutsummaryrefslogtreecommitdiffstats
path: root/src/ngScenario/Scenario.js
AgeCommit message (Collapse)Author
2013-12-30fix(input): prevent double $digest when using jQuery trigger.Michał Gołębiowski
If an event was performed natively, jQuery sets the isTrigger property. When triggering event manually, the field is not present. Manually triggered events are performed synchronously which causes the "$digest already in progress" error. Closes #5293
2013-10-22style: make jshint happyVojta Jina
2013-09-25fix(ngScenario): fix error message descriptionPete Bacon Darwin
2013-09-18fix(scenario): include "not " in error messages if test is invertedHubert SABLONNIÈRE
Closes #3840
2013-07-31feat(scenario): expose jQuery for usage outside of angular scenarioAndreas Marek
The global jQuery reference is removed by angular scenario and only a local scoped reference is kept. To make jQuery available for other code, a new reference angular.scenario.jQuery is added.
2013-05-14feat(scenario): adds mousedown and mouseup event triggers to scenarioAndreas Marek
Added mousedown and mouseup event triggers to scenadio dsl 'element' expression. Added mousedown and mouseup to the custom jquery trigger method to generate real events.
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.
2013-03-29docs(*): fixed typosPascal Borreli
2013-03-13feat(ngMobile): add ngMobile module with mobile-specific ngClickBraden Shepherdson
Add a new module ngMobile, with mobile/touch-specific directives. Add ngClick, which overrides the default ngClick. This ngClick uses touch events, which are much faster on mobile. On desktop browsers, ngClick responds to click events, so it can be used for portable sites.
2012-09-11fix(scenario): NPE when no angular loaded in test pageJimmy Zhuo
2012-04-10chore(*): remove dead code and fix code style issuesIgor Minar
2012-04-03feat(ngModel): update model on each key stroke (revert ngModelInstant)Vojta Jina
It turns out that listening only on "blur" event is not sufficient in many scenarios, especially when you use form validation you always had to use ngModelnstant e.g. if you want to disable a button based on valid/invalid form. The feedback we got from our apps as well as external apps is that the ngModelInstant should be the default. In the future we might provide alternative ways of suppressing updates on each key stroke, but it's not going to be the default behavior. Apps already using the ngModelInstant can safely remove it from their templates. Input fields without ngModelInstant directive will start propagating the input changes into the model on each key stroke.
2012-03-28chore(module): move files around in preparation for more modulesMisko Hevery