Skip to content

Using AngularJS in a Chrome Extension environment

Jump to bottom Edit New page
victorbstan edited this page Jul 7, 2012 · 1 revision

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>
Add a custom footer

Navigation

Clone this wiki locally