| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2012-05-05 | fix(scenario): make browser().location() working if ng-app on other than <html> | Vojta Jina | |
| 2012-04-20 | chore(license): update to google | Misko Hevery | |
| 2012-04-12 | fix(e2eRunner): $browser.location should delegate to apps $location | Igor Minar | |
| previously it would create a new instance which wasn't configured as the one in the app, which resulted in incorrect values being returned in html5 mode with base url set | |||
| 2012-04-10 | chore(*): remove dead code and fix code style issues | Igor Minar | |
| 2012-04-03 | feat(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-28 | chore(module): move files around in preparation for more modules | Misko Hevery | |
