angular.js/src/ngScenario, branch v1.0.4 fix(scenario): don't trigger input events on IE9 2013-01-17T07:30:16+00:00 Igor Minar 2013-01-16T18:51:24+00:00 92c612a9deac6e311bc2c632d373d525bf9017a0 input.enter() should trigger 'change' rather than 'input' event on IE9 because input events on IE9 are broken and angular doesn't rely on them 
input.enter() should trigger 'change' rather than 'input' event on IE9 because
input events on IE9 are broken and angular doesn't rely on them
fix(scenario-runner): support data-ng and x-ng based attributes 2012-10-31T21:10:26+00:00 Adam Macejak 2012-10-30T01:54:26+00:00 ad7ce0d40216cf3e0a721ef3a4815a03ae9f0bd9 Prefixed attributes like data-ng-model and x-ng-model were not being found by the Selector. It was only looking at ng: and ng- prefixed attributes. Added a few tests as well to ensure the aforementioned prefixed attributes are being matched properly. Closes #1020 
Prefixed attributes like data-ng-model and x-ng-model were not being
found by the Selector. It was only looking at ng: and ng- prefixed
attributes.
Added a few tests as well to ensure the aforementioned prefixed
attributes are being matched properly.

Closes #1020
fix(scenario): emit RunnerBegin event 2012-09-11T23:19:44+00:00 Shyam Seshadri 2012-09-07T05:14:46+00:00 bf873d6f0275c14c603fe0d437d77d531cb93c62 






fix(scenario): NPE when no angular loaded in test page
2012-09-11T23:19:44+00:00

Jimmy Zhuo

2012-09-08T04:46:24+00:00

82f4b99d994bd2dcb970c38e86a8ca0249c167bc












docs(*): simplify doc urls
2012-06-12T07:10:18+00:00

Igor Minar

2012-06-12T06:49:24+00:00

f16150d5f1b20b3d633b4402095ea89baa4be042

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





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







fix(scenario): make browser().location() working if ng-app on other than <html>
2012-05-05T01:30:28+00:00

Vojta Jina

2012-04-14T17:39:24+00:00

5bcb749abb91dba0847cb9bc900777a67fd55aa8












chore(license): update to google
2012-04-20T18:29:34+00:00

Misko Hevery

2012-04-17T22:17:04+00:00

ce15a3e0491f7acafcdf0ff07f75d0c2c9819164












fix(e2eRunner): $browser.location should delegate to apps $location
2012-04-12T09:36:03+00:00

Igor Minar

2012-04-12T09:15:36+00:00

df72852f3496d7640bb4f70837338e464b7ed69f

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





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







chore(*): remove dead code and fix code style issues
2012-04-10T23:52:12+00:00

Igor Minar

2012-04-10T21:29:49+00:00

52ee1ab5eb0f3197453b26c60a70239ac3fffea7












feat(ngModel): update model on each key stroke (revert ngModelInstant)
2012-04-03T17:10:44+00:00

Vojta Jina

2012-03-30T19:07:19+00:00

06d0955074f79de553cc34fbf945045dc458e064

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.





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.