aboutsummaryrefslogtreecommitdiffstats
path: root/src/ngScenario/Scenario.js
AgeCommit message (Collapse)Author
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
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