For CSS that's safe to source into the application.
For CSS that's safe to source into the application. Currently unused. Feel free to use it in your own directives.
For HTML that's safe to source into the application.
For HTML that's safe to source into the application. The ngBindHtml directive uses this context for bindings. If an unsafe value is encountered and the $sanitize module is present this will sanitize the value instead of throwing an error.
For JavaScript that is safe to execute in your application's context.
For JavaScript that is safe to execute in your application's context. Currently unused. Feel free to use it in your own directives.
For URLs that are not only safe to follow as links, but whose contents are also safe to include in your application.
For URLs that are not only safe to follow as links, but whose contents are also safe to include in your application. Examples include ng-include, src / ngSrc bindings for tags other than IMG (e.g. IFRAME, OBJECT, etc.)
Note that $sce.RESOURCE_URL makes a stronger statement about the URL than $sce.URL does and therefore contexts requiring values trusted for $sce.RESOURCE_URL can be used anywhere that values trusted for $sce.URL are required.
For URLs that are safe to follow as links.
For URLs that are safe to follow as links. Currently unused (<a href= and <img src= sanitize their urls and don't constitute an SCE context.
SCE Service Singleton