Vojta Jina 06d0955074 feat(ngModel): update model on each key stroke (revert ngModelInstant) ... 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-04-03 10:10:44 -07:00
..
api	docs(input): Fix some broken links, add missing $, use ng- in examples	2012-03-13 13:52:57 -07:00
cookbook	feat($compile): do not interpolate boolean attributes, rather evaluate them	2012-03-26 21:14:09 -07:00
guide	feat(ngModel): update model on each key stroke (revert ngModelInstant)	2012-04-03 10:10:44 -07:00
misc	docs(guide/started): fix examples	2012-03-20 11:30:21 -07:00