angular.js/src/ng/directive, branch v1.0.0rc10 fix(ngRepeat): expose $first, $middle and $last instead of $position 2012-05-22T21:18:15+00:00 Max 2012-05-02T16:51:31+00:00 1d388676e3b97b6171fc498e82545bd437ee6fd1 $position marker doesn't work well in cases when we have just one item in the list because then the item is both the first and last. To solve this properly we need to expose individual $first and $middle and $last flags. BREAKING CHANGE: $position is not exposed in repeater scopes any more To update, search for $position and replace it with one of $first, $middle or $last. Closes #912 
$position marker doesn't work well in cases when we have just one item
in the list because then the item is both the first and last. To solve
this properly we need to expose individual $first and $middle and $last
flags.

BREAKING CHANGE: $position is not exposed in repeater scopes any more

To update, search for $position and replace it with one of $first,
$middle or $last.

Closes #912
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
chore(docs): re-skin main documentation 2012-05-04T23:12:17+00:00 Misko Hevery 2012-04-29T05:45:28+00:00 8e2675029f5ca404a7c649cc161df3ea642d941f 






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







docs(ngCsp): make the CSP docs publicly visible
2012-04-30T22:37:12+00:00

Igor Minar

2012-04-30T22:37:12+00:00

96758c1c5277ca9041e82c4c1d2e2c473cd477b0












docs(ngSanitize): fix directive links
2012-04-30T08:09:55+00:00

Igor Minar

2012-04-30T08:09:55+00:00

006fb4fbeb768e4b50659838f7587bae9847371d












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.







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.