angular.js/test/ng/directive, branch v1.0.0rc9 fix(ngSrc,ngHref): binding should set element prop as well as attr 2012-05-07T06:01:33+00:00 Igor Minar 2012-05-06T23:30:24+00:00 b24cc63bcbd45741d21757653f05d54db09e0f20 IE9 ignores setAttribute('src', val) calls on img if "ng:src" attribute is present. It only fetches the image if element property is updated as well. Closes #935 
IE9 ignores setAttribute('src', val) calls on img if "ng:src" attribute
is present. It only fetches the image if element property is updated as well.

Closes #935
fix(ngModel): use keydown/change events on IE9 instead of input 2012-05-07T06:01:33+00:00 Igor Minar 2012-05-06T16:27:10+00:00 49dfdf8f0238ef8c473fcb44694f6b5696ecde70 On IE9 the input event is not fired when backspace or delete key are pressed or when cut is performed. This makes listening on the input event unreliable and therefore it's better for us to just use keydown/change events instead. Closes #879 
On IE9 the input event is not fired when backspace or delete key are pressed or when
cut is performed. This makes listening on the input event unreliable and therefore
it's better for us to just use keydown/change events instead.

Closes #879
fix(select): don't interfere with selection if not databound 2012-05-02T21:24:43+00:00 Igor Minar 2012-05-02T07:33:00+00:00 3bd3cc571dcd721f9d71f971aefee23115a5e458 Closes #926 
Closes #926
feat($parse): CSP compatibility 2012-04-28T06:04:24+00:00 Igor Minar 2012-04-27T22:20:54+00:00 2b87c814ab70eaaff6359ce1a118f348c8bd2197 CSP (content security policy) forbids apps to use eval or Function(string) generated functions (among other things). For us to be compatible, we just need to implement the "getterFn" in $parse without violating any of these restrictions. We currently use Function(string) generated functions as a speed optimization. With this change, it will be possible to opt into the CSP compatible mode using the ngCsp directive. When this mode is on Angular will evaluate all expressions up to 30% slower than in non-CSP mode, but no security violations will be raised. In order to use this feature put ngCsp directive on the root element of the application. For example: <!doctype html> <html ng-app ng-csp> ... ... </html> Closes #893 
CSP (content security policy) forbids apps to use eval or
Function(string) generated functions (among other things). For us to be
compatible, we just need to implement the "getterFn" in $parse without
violating any of these restrictions.

We currently use Function(string) generated functions as a speed
optimization. With this change, it will be possible to opt into the CSP
compatible mode using the ngCsp directive. When this mode is on Angular
will evaluate all expressions up to 30% slower than in non-CSP mode, but
no security violations will be raised.

In order to use this feature put ngCsp directive on the root element of
the application. For example:

<!doctype html>
<html ng-app ng-csp>
  ...
  ...
</html>

Closes #893
fix(select): properly handle empty & unknown options without ngOptions 2012-04-20T21:29:37+00:00 Igor Minar 2012-04-18T07:48:25+00:00 904b69c745ea4afc1d6ecd2a5f3138c6f947b157 Previously only when ngOptions was used, we correctly handled situations when model was set to an unknown value. With this change, we'll add/remove extra unknown option or reuse an existing empty option (option with value set to "") when model is undefined. 
Previously only when ngOptions was used, we correctly handled situations
when model was set to an unknown value. With this change, we'll add/remove
extra unknown option or reuse an existing empty option (option with value
set to "") when model is undefined.
test(selectSpec): clean up and simplify specs 2012-04-20T21:29:36+00:00 Igor Minar 2012-04-17T22:12:09+00:00 c65c34ebfe0f70c83a45f283654c8558802752cf 






fix(script): Incorrectly reading script text on ie
2012-04-20T18:29:34+00:00

Misko Hevery

2012-04-17T20:55:10+00:00

94dd68570952f6f31abfa351b1159afcd3588a57

IE deals with script tags in special way and .text() does not work. Reading the .text property directly fixes the issue.





IE deals with script tags in special way and .text() does not work. Reading the .text property directly fixes the issue.







fix(input.radio): support 2-way binding in a repeater
2012-04-11T22:50:52+00:00

Vojta Jina

2012-04-10T20:41:51+00:00

93d62860e988a09fb64e594f50f6cd55a1fc5748

Closes #869





Closes #869







chore(ngSanitize): extract $sanitize, ngBindHtml, linkyFilter into a module
2012-04-11T22:50:47+00:00

Vojta Jina

2012-04-10T23:50:31+00:00

5bcd7198664dca2bf85ddf8b3a89f417cd4e4796

Create build for other modules as well (ngResource, ngCookies):
- wrap into a function
- add license
- add version

Breaks `$sanitize` service, `ngBindHtml` directive and `linky` filter were moved to the `ngSanitize` module. Apps that depend on any of these will need to load `angular-sanitize.js` and include `ngSanitize` in their dependency list: `var myApp = angular.module('myApp', ['ngSanitize']);`





Create build for other modules as well (ngResource, ngCookies):
- wrap into a function
- add license
- add version

Breaks `$sanitize` service, `ngBindHtml` directive and `linky` filter were moved to the `ngSanitize` module. Apps that depend on any of these will need to load `angular-sanitize.js` and include `ngSanitize` in their dependency list: `var myApp = angular.module('myApp', ['ngSanitize']);`







chore(ngBind): remove obsolete test
2012-04-09T18:49:51+00:00

Igor Minar

2012-04-09T18:49:43+00:00

b5406d276d73bcb0319eb451fa1cf2aec1e67946

this test is not testing what it claims it is.

we don't need it any more





this test is not testing what it claims it is.

we don't need it any more