angular.js, branch v1.0.0rc7 chore(release): cut 1.0.0rc7 rc-generation release 2012-04-30T23:32:45+00:00 Igor Minar 2012-04-30T23:32:45+00:00 76afa406b1be0105149290d4716b735457518a47 






docs(changelog): release notes for 1.0.0rc7 rc-generation
2012-04-30T22:53:05+00:00

Igor Minar

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

f3c77858be536238884d5dd44855328b3a521e5e












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












docs(tutorial): update all the remaining steps
2012-04-30T08:08:15+00:00

Igor Minar

2012-04-27T22:18:54+00:00

075c089b5cbe72e95ec96638f8925aeb44824f7c

I made some diagrams and portions of the text that are stil stale
invisible. We'll fix these in the next relese.





I made some diagrams and portions of the text that are stil stale
invisible. We'll fix these in the next relese.







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







chore(server.js): Add CSP support
2012-04-28T05:04:16+00:00

Igor Minar

2012-04-27T22:20:34+00:00

2b1b2570344cfb55ba93b6f184bd3ee6db324419

The support is disabled by default, uncomment relevant lines to enable
it.





The support is disabled by default, uncomment relevant lines to enable
it.







chore(check-size): add a script to check gziped size
2012-04-23T18:42:27+00:00

Igor Minar

2012-03-16T23:09:41+00:00

73caf76225b1a1ab41bca00340950985633f9ef9

this is useful to quickly check the resulting size during development





this is useful to quickly check the resulting size during development







chore(release): start 1.0.0rc7 rc-generation iteration
2012-04-23T18:42:26+00:00

Igor Minar

2012-04-21T00:05:28+00:00

dbb92efd13cd0171da369645f8780fde9987a78f












docs(directive): fix transclusion examples
2012-04-21T19:08:30+00:00

Vojta Jina

2012-04-21T19:08:30+00:00

1214084e9d036c4968adb2b15c4cbedd763c215d