aboutsummaryrefslogtreecommitdiffstats
path: root/src/ngScenario/dsl.js
AgeCommit message (Collapse)Author
2012-09-06feat(scenario): add dblclick method to the ngScenario dslPedro Del Gallego
2012-06-12docs(*): simplify doc urlsIgor Minar
we now have two types of namespaces: - true namespace: angular.* - used for all global apis - virtual namespace: ng.*, ngMock.*, ... - used for all DI modules the virual namespaces have services under the second namespace level (e.g. ng.) and filters and directives prefixed with filter: and directive: respectively (e.g. ng.filter:orderBy, ng.directive:ngRepeat) this simplifies urls and makes them a lot shorter while still avoiding name collisions
2012-05-05fix(scenario): make browser().location() working if ng-app on other than <html>Vojta Jina
2012-04-12fix(e2eRunner): $browser.location should delegate to apps $locationIgor 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-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